Server and method for providing connected service

ABSTRACT

A method for providing a connected service of an image capturing apparatus for a vehicle is provided. The method includes connecting the image capturing apparatus for a vehicle to a server for providing a connected service using a wireless communication module; generating event data including event code information and operation mode information of the image capturing apparatus for a vehicle, when an event occurs in the image capturing apparatus for a vehicle; and transmitting the generated event data to the server for providing a connected service through the wireless communication module.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. application Ser. No.16/987,848, filed on Aug. 7, 2020 and issued on Sep. 20, 2022 as a U.S.Pat. No. 11,451,701, which claims benefit of priority to Korean PatentApplication No. 10-2019-0097009 filed on Aug. 8, 2019, 10-2020-0087298filed on Jul. 15, 2020 and 10-2020-0091801 filed on Jul. 23, 2020 in theKorean Intellectual Property Office, the disclosure of which isincorporated herein by reference in its entirety.

BACKGROUND 1. Field

The present invention relates to an image capturing apparatus for avehicle, a server, a user terminal device, and a method for providing aconnected service using the same that provide the connected service tothe vehicle by utilizing a wireless communication network.

2. Description of Related Art

An image capturing apparatus for a vehicle, which is an apparatus thatrecords images captured during driving, stopping, and parking of thevehicle, is very importantly used in identifying a cause of a vehicle'saccident. Accordingly, in recent years, the number of vehicles equippedwith the image capturing apparatus has been increasing.

Since the images captured by the image capturing apparatus for a vehicleinclude the images captured during driving, stopping, and parking of thevehicle and location information where the images were captured, theimage capturing apparatus for a vehicle may further enhance a drivingconvenience for a driver and provide various functions or servicesutilizing such information.

SUMMARY

An object of the present invention is to implement a connected servicethat provides various meaningful information about a vehicle to a userof a user terminal device and receives various control commands from theuser to control an operation of an image capturing apparatus for thevehicle, by enabling communication between the image capturing apparatusfor the vehicle and the user terminal device.

According to an exemplary embodiment of the present invention, a methodfor providing a connected service of a server for providing theconnected service, includes: storing service subscription informationincluding information of a subscriber subscribed to a service andapparatus information of the subscriber; receiving a terminalregistration request from an image capturing apparatus for a vehicle;determining validity of the terminal registration request by comparingidentification information corresponding to the terminal registrationrequest with pre-stored service subscription information; registeringthe image capturing apparatus for a vehicle as an apparatus suppliedwith a service when it is determined that the terminal registrationrequest is valid; and receiving operation data generated in an operationprocess of the registered image capturing apparatus for a vehicle andstoring the received operation data.

The operation data may include at least one of event data correspondingto an event occurring in the image capturing apparatus for a vehicle,image data captured in the image capturing apparatus for a vehicle, andlocation data of the image capturing apparatus for a vehicle.

The method for providing a connected service may further include:searching for identification information and/or subscriberidentification information of a user terminal device corresponding theimage capturing apparatus for a vehicle that transmits the operationdata based on the stored service subscription information; generating anotification message to be transmitted to the user terminal device basedon the searched information; and transmitting the generated notificationmessage to the user terminal device.

The method for providing a connected service may further include, whenoperation data corresponding to the notification message is requestedfrom the user terminal device, transmitting the operation datacorresponding to the request of the user terminal device to the userterminal device.

The method for providing a connected service may further include:receiving a service provision request from the user terminal device;searching for subscriber identification information corresponding to auser terminal device requesting the service provision based on thestored service subscription information; and detecting the operationdata corresponding to the searched subscriber identificationinformation.

The method for providing a connected service may further include:providing the type of the detected operation data to the user terminaldevice; and transmitting operation data corresponding to a request ofthe user terminal device to the user terminal device when the provisionof the operation data requested based on the type of the detectedoperation data from the user terminal device.

The terminal registration request of the image capturing apparatus for avehicle may include at least one of identification information of theimage capturing apparatus for a vehicle and identification informationof a communication module included in the image capturing apparatus fora vehicle.

The terminal registration request of the user terminal device mayinclude at least one of identification information of the user terminaldevice and identification information of a user for the user terminaldevice.

According to an exemplary embodiment of the present invention, a methodfor providing a connected service of an image capturing apparatus for avehicle, includes: connecting the image capturing apparatus for avehicle to a server for providing a connected service using a wirelesscommunication module; generating event data including event codeinformation and operation mode information of the image capturingapparatus for a vehicle, when an event occurs in the image capturingapparatus for a vehicle; and transmitting the generated event data tothe server for providing a connected service through the wirelesscommunication module.

The event may include a first event includes at least one of an impactoccurrence event while parked, an impact occurrence event while driving,and a movement occurrence event while parked, the method may furtherinclude extracting at least two images of images captured within apredetermined time range of an occurrence of the first event when thefirst event occurs, and generating image upload data using the extractedimages, and in the transmitting of the generated event data, the firstevent data and the image upload data may be transmitted to the serverfor providing a connected service through the wireless communicationmodule.

The image upload data may include total image count information.

The event may include a second event including at least one of a parkinglocation image request response event and a live image request responseevent according to a request in the user terminal device provided withthe connected service, the method may further include extracting animage of a time point corresponding to the second event when the secondevent occurs and generating image upload data, and in the transmittingof the generated event data, the second event data and the image uploaddata may be transmitted to the server for providing a connected servicethrough the wireless communication module.

The event may include a third event corresponding to an advance drivingassistance system (ADAS) event, and the method may further includegenerating third event data including the type of the third event, anoccurrence time of the third event, and an occurrence location of thethird event, when the third event occurs.

The ADAS may include at least two of a front vehicle start notification,a front vehicle collision notification, and a lane departurenotification.

The method for providing a connected service may further include:generating data for terminal registration request of the image capturingapparatus for a vehicle upon initial connection of the image capturingapparatus for a vehicle and transmitting the generated data to theserver for providing a connected service through the wirelesscommunication module; and receiving registration request response dataincluding at least one of a traffic information day use time limit, aparking location image remaining count, a live image remaining count,and an impact image remaining count from the server for providing aconnected service as a response to the terminal registration request.

The terminal registration request may be repeatedly performed wheneverthe power of the image capturing apparatus for a vehicle is turned on.

The wireless communication module may be NB-IOT or CAT-M1.

In the generating of the image upload data, the image capturingapparatus for a vehicle may adjust a size of data to be transmitted tothe server in consideration of data communication speed with the serverfor providing a connected service, a state of a battery of the imagecapturing apparatus for a vehicle, and a size of a storage spaceallocated to the server for providing a connected service.

According to an exemplary embodiment of the present invention, a methodfor providing a connected service of a user terminal device, includes:accessing a server for providing a connected service; receiving datatransmitted from an image capturing apparatus for a vehicle to theserver for providing a connected service; and generating a userinterface based on the received data and displaying the generated userinterface, wherein the user interface includes a main user interface,and the main user interface displays at least two of connection stateinformation of a connected image capturing apparatus for a vehicle, anoperation mode of the image capturing apparatus for a vehicle, whetheror not an impact event of the vehicle occurs, and whether or not amovement event of the vehicle occurs.

A vehicle image may be displayed on one region of the main userinterface, and whether or not the impact event of the vehicle occurs andwhether or not the movement event of the vehicle occurs may be displayedby an icon on the vehicle image.

A vehicle image may be displayed on one region of the main userinterface, and the operation mode of the image capturing apparatus for avehicle may include a normal recording mode and a parking recordingmode, and a border of the vehicle image in the normal recording mode andthe parking recording mode may be distinguished and displayed indifferent colors.

The user interface may include a driving information display region fordisplaying a driving record for a predetermined period of a vehicledriver, the driving record may include at least one of suddendeceleration, sudden acceleration, over-speed, forward collisionwarning, and lane departure warning, and the driving information displayregion may display the driving record by adjusting a size of a figureaccording to the number of times of each type of driving record.

The user interface may include the last parking location user interface,the last parking location user interface may display an image for thelast parking location, and the image for the last parking location maybe an image captured at a predetermined time point during a switchingperiod, when the image capturing apparatus for a vehicle is switchedfrom a normal recording mode to a parking recording mode according to astart-off after a parking of the vehicle is completed.

The user interface may include the last parking location user interface,and the last parking location user interface may display a currentlocation of a user and the last parking location of the vehicle on amap, and display a relationship between both locations by connecting thecurrent location of the user and the last parking location of thevehicle with a line.

The user interface may include an event user interface corresponding toan impact event or a movement event, the event user interface maydisplay an event image, and the event image may be a motion imagegenerated by combining at least two images between a predetermined timebefore an event occurrence and a predetermined time after the eventoccurrence.

The user interface may include a live user interface for displaying alive image, and the live image may be a motion image generated bycombining at least two images after a live image request time point.

The live user interface may further display remaining available countinformation of the live image.

According to an exemplary embodiment of the present invention, a serverfor providing a connected service includes: a storage unit storingservice subscription information including information of a subscribersubscribed to a service and apparatus information of the subscriber; acommunication unit receiving a terminal registration request from animage capturing apparatus for a vehicle; and a control unit determiningvalidity of the terminal registration request by comparingidentification information corresponding to the terminal registrationrequest with pre-stored service subscription information, andregistering the image capturing apparatus for a vehicle as an apparatusprovided with the service when it is determined that the terminalregistration request is valid, wherein the control unit controls tostore received operation data in the storage unit, when operation datagenerated in an operation process of the registered image capturingapparatus for a vehicle is received through the communication unit.

The operation data may include at least one of event data correspondingto an event occurring in the image capturing apparatus for a vehicle,image data captured in the image capturing apparatus for a vehicle, andlocation data of the image capturing apparatus for a vehicle.

The control unit may search for identification information and/orsubscriber identification information of a user terminal devicecorresponding the image capturing apparatus for a vehicle that transmitsthe operation data based on the stored service subscription information,generate a notification message to be transmitted to the user terminaldevice based on the searched information, and control the communicationunit to transmit the generated notification message to the user terminaldevice.

When operation data corresponding to the notification message isrequested from the user terminal device, the control unit may controlthe communication unit to transmit the operation data corresponding tothe request of the user terminal device to the user terminal device.

When a service provision request is received from the user terminaldevice, the control unit may search for subscriber identificationinformation corresponding to a user terminal device requesting theservice provision based on the stored service subscription information,and detect the operation data corresponding to the searched subscriberidentification information.

The control unit may control the communication unit to provide the typeof the detected operation data to the user terminal device, and controlthe communication unit to transmit operation data corresponding to arequest of the user terminal device to the user terminal device when theprovision of the operation data is requested based on the type of thedetected operation data from the user terminal device.

The terminal registration request of the image capturing apparatus for avehicle may include at least one of identification information of theimage capturing apparatus for a vehicle and identification informationof a communication module included in the image capturing apparatus fora vehicle.

The terminal registration request of the user terminal device mayinclude at least one of identification information of the user terminaldevice and identification information of a user for the user terminaldevice.

According to an exemplary embodiment of the present invention, an imagecapturing apparatus fora vehicle includes: a communication unitcommunicating with a server for providing a connected service; and acontrol unit generating event data including event code information andoperation mode information of the image capturing apparatus for avehicle, when an event occurs in the image capturing apparatus for avehicle, and controlling the communication unit to transmit thegenerated event data to the server for providing a connected service.

The event may include a first event includes at least one of an impactoccurrence event while parked, an impact occurrence event while driving,and a movement occurrence event while parked, the control unit mayextracts at least two images of images captured within a predeterminedtime range of an occurrence of the first event when the first eventoccurs, and generates image upload data using the extracted images, andtransmits the first event data and the image upload data to the serverfor providing a connected service through the communication unit.

The image upload data may include total image count information.

The event may include a second event including at least one of a parkinglocation image request response event and a live image request responseevent according to a request in the user terminal device provided withthe connected service, the control unit may extract an image of a timepoint corresponding to the second event when the second event occurs andgenerates image upload data, and transmit the second event data and theimage upload data to the server for providing a connected servicethrough the communication unit.

The event may include a third event corresponding to an advance drivingassistance system (ADAS) event, and the control unit may generate thirdevent data including the type of the third event, an occurrence time ofthe third event, and an occurrence location of the third event, when thethird event occurs.

The ADAS may include at least two of a front vehicle start notification,a front vehicle collision notification, and a lane departurenotification.

The control unit may controls to generate data for terminal registrationrequest of the image capturing apparatus for a vehicle upon initialconnection of the image capturing apparatus for a vehicle and transmitthe generated data to the server for providing a connected servicethrough the communication unit, and the communication unit may receiveregistration request response data including at least one of a trafficinformation day use time limit, a parking location image remainingcount, a live image remaining count, and an impact image remaining countfrom the server for providing a connected service as a response to theterminal registration request.

The terminal registration request may be repeatedly performed wheneverthe power of the image capturing apparatus for a vehicle is turned on.

The communication unit may be NB-IOT or CAT-M1.

The control unit may adjust a size of data to be transmitted to theserver in consideration of data communication speed of the imagecapturing apparatus for a vehicle with the server for providing aconnected service, a state of a battery of the image capturing apparatusfor a vehicle, and a size of a storage space allocated to the server forproviding a connected service.

According to an exemplary embodiment of the present invention, a userterminal device includes: a display unit; a communication unit accessinga server for providing a connected service and receiving datatransmitted from an image capturing apparatus for a vehicle to theserver for providing a connected service; and a control unit generatinga user interface based on the received data and controlling the displayunit to display the generated user interface, wherein the user interfaceincludes a main user interface, and the main user interface displays atleast two of connection state information of a connected image capturingapparatus for a vehicle, an operation mode of the image capturingapparatus for a vehicle, whether or not an impact event of the vehicleoccurs, and whether or not a movement event of the vehicle occurs.

A vehicle image may be displayed on one region of the main userinterface, and whether or not the impact event of the vehicle occurs andwhether or not the movement event of the vehicle occurs may be displayedby an icon on the vehicle image.

A vehicle image may be displayed on one region of the main userinterface, and the operation mode of the image capturing apparatus for avehicle may include a normal recording mode and a parking recordingmode, and a border of the vehicle image in the normal recording mode andthe parking recording mode may be distinguished and displayed indifferent colors.

The user interface may include a driving information display region fordisplaying a driving record for a predetermined period of a vehicledriver, the driving record may include at least one of suddendeceleration, sudden acceleration, over-speed, forward collisionwarning, and lane departure warning, and the driving information displayregion may display the driving record by adjusting a size of a figureaccording to the number of times of each type of driving record.

The user interface may include the last parking location user interface,the last parking location user interface may display an image for thelast parking location, and the image for the last parking location maybe an image captured at a predetermined time point during a switchingperiod, when the image capturing apparatus for a vehicle is switchedfrom a normal recording mode to a parking recording mode according to astart-off after a parking of the vehicle is completed.

The user interface may include the last parking location user interface,and the last parking location user interface may display a currentlocation of a user and the last parking location of the vehicle on amap, and display a relationship between both locations by connecting thecurrent location of the user and the last parking location of thevehicle with a line.

The user interface may include an event user interface corresponding toan impact event or a movement event, the event user interface maydisplay an event image, and the event image may be a motion imagegenerated by combining at least two images between a predetermined timebefore an event occurrence and a predetermined time after the eventoccurrence.

The user interface may include a live user interface for displaying alive image, and the live image may be a motion image generated bycombining at least two images after a live image request time point.

The live user interface may further display remaining available countinformation of the live image.

According to an exemplary embodiment of the present invention, acomputer readable recording medium in which a program code for executingthe method for providing a connected service described above is recordedmay be provided.

According to an exemplary embodiment of the present invention, acomputer program including a program code for executing the method forproviding a connected service described above may be provided.

According to an exemplary embodiment of the present invention, a varietyof meaningful information about the vehicle may be provided to the userof the user terminal device by providing the information generated inthe image capturing apparatus for the vehicle to the server and the userterminal device through the wireless communication network. As anexample, it is possible to enable the connected service connectedbetween the vehicle, the image capturing apparatus for the vehicle, andthe server, by exchanging a variety of data such as an image, a parkinglocation, a parking time, whether impact/movement events are detected,and an ADAS driving record collected from the image capturing apparatusfor the vehicle with the server and the user terminal device through thewireless communication network, and accordingly, it is possible toincrease the convenience of the user having the vehicle and the imagecapturing apparatus for the vehicle.

Further, according to an exemplary embodiment of the present invention,the connected service that provides a variety of meaningful informationabout the vehicle to the user of the user terminal device may beimplemented by applying low-power wide area communication-based Internetof Things (IoT) technology to the image capturing apparatus for thevehicle. As an example, more advanced functions may be expanded intransmission speed, transmission amount, power efficiency, and the likethrough the low-power wide area communication device, and a hand-overfunction that may monitor the vehicle at all times while driving may beapplied.

Further, according to the present invention, an interworking protocolbetween the low-power wide area communication apparatus and the serverfor the connected service may be provided.

Meanwhile, the effects obtainable in the present invention are notlimited to the effects mentioned above, and other effects that are notmentioned may be obviously understood by those skilled in the art towhich the present invention pertains from the following description.

BRIEF DESCRIPTION OF DRAWINGS

The above and other aspects, features and other advantages of thepresent disclosure will be more clearly understood from the followingdetailed description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a block diagram illustrating a connected service systemaccording to an exemplary embodiment of the present invention.

FIG. 2 is a block diagram illustrating an image capturing apparatus fora vehicle according to an exemplary embodiment of the present invention.

FIG. 3 is a block diagram illustrating a user terminal device accordingto an exemplary embodiment of the present invention.

FIG. 4 is a block diagram illustrating a server for providing aconnected service according to an exemplary embodiment of the presentinvention.

FIG. 5 is a timing diagram illustrating an operation scenario of aconnected service system in black box registration and user registrationprocesses according to the present invention.

FIG. 6 is a timing diagram illustrating an operation scenario of aconnected service system in an event registration process according toan exemplary embodiment of the present invention.

FIG. 7 is a timing diagram illustrating an operation scenario of aconnected service system when uploading an image from a black boxaccording to an exemplary embodiment of the present invention.

FIG. 8 is a timing diagram illustrating an operation scenario of aconnected service system when an image is requested by a user terminaldevice according to an exemplary embodiment of the present invention.

FIG. 9 is a timing diagram illustrating an operation scenario of aconnected service system when a power off request is made in a black boxaccording to an exemplary embodiment of the present invention.

FIG. 10 is a timing diagram illustrating an operation scenario of aconnected service system when a black box is powered off according to arequest of a user terminal device according to an exemplary embodimentof the present invention.

FIG. 11 is a timing diagram illustrating a motion image registrationprocess according to an exemplary embodiment of the present invention.

FIGS. 12A to 12C are diagrams illustrating a main user interfaceaccording to an exemplary embodiment of the present invention.

FIGS. 13A to 13C are user interface diagrams illustrating a refreshprocess of the main user interface according to an exemplary embodimentof the present invention.

FIGS. 14A to 14B are user interface diagrams illustrating a black boxregistration process through the main user interface according to anexemplary embodiment of the present invention.

FIGS. 15A to 15B are diagrams illustrating a user interface of a lastparking location according to an exemplary embodiment of the presentinvention.

FIG. 16 is a diagram illustrating a user interface displaying a user'scurrent location and a last parking location according to an exemplaryembodiment of the present invention.

FIGS. 17A to 17C are user interface diagrams illustrating a process forsharing a last parking location image according to an exemplaryembodiment of the present invention.

FIGS. 18A to 18E are user interface diagrams illustrating a process forsharing a last parking location according to an exemplary embodiment ofthe present invention.

FIGS. 19A to 21B are diagrams illustrating a user interface for managingparking history according to an exemplary embodiment of the presentinvention.

FIGS. 22A to 22D are diagrams illustrating a user interface in asituation of an impact event of the vehicle or a movement event of thevehicle according to an exemplary embodiment of the present invention.

FIGS. 23A to 23C are diagrams illustrating a user interface wheninputting a live command according to an exemplary embodiment of thepresent invention.

FIGS. 24A to 24B are user interface diagrams illustrating live historyimage management according to an exemplary embodiment of the presentinvention.

FIGS. 25A to 25F are user interface diagrams illustrating a method forswitching an image display according to an exemplary embodiment of thepresent invention.

FIGS. 26A to 26B are diagrams illustrating an environment setting userinterface according to an exemplary embodiment of the present invention.

FIGS. 27A to 27C are diagrams illustrating a user interface illustratinga coupon usage process according to an exemplary embodiment of thepresent invention.

FIGS. 28A to 28C are diagrams illustrating a user interface for guidinga route to a coupon available dealer according to an exemplaryembodiment of the present invention.

FIGS. 29A to 29B are user interface diagrams illustrating an emergencySOS notification setting process according to an exemplary embodiment ofthe present invention.

FIGS. 30A to 30C are user interface diagrams illustrating an emergencySOS contact registration process according to an exemplary embodiment ofthe present invention.

FIGS. 31A to 31B are user interface diagrams illustrating a processingscenario when an emergency situation occurs according to an exemplaryembodiment of the present invention.

FIG. 32 is a diagram illustrating an example of a push notificationaccording to an exemplary embodiment of the present invention.

FIGS. 33A to 33F are diagrams illustrating a user interface for a remoteplayback request in a normal recording mode state of a black boxaccording to an exemplary embodiment of the present invention.

FIG. 34 is a diagram illustrating a remote playback scenario in thenormal recording mode state of the black box according to an exemplaryembodiment of the present invention.

FIG. 35 is a diagram illustrating an operation scenario of a black boxwhen an additional playback request is received during image playbackaccording to an exemplary embodiment of the present invention.

FIGS. 36A to 36F are diagrams illustrating a user interface for a remoteplayback request in a parking mode state of the black box according toan exemplary embodiment of the present invention.

FIG. 37 is a diagram illustrating an operation scenario of the black boxwhen the black box is switched from the parking mode state to the normalmode state according to an embodiment of the present invention.

FIGS. 38A to 38B are block diagrams illustrating a server for providinga connected service according to an exemplary embodiment of the presentinvention.

FIGS. 39A to 39C are diagrams illustrating a user interface forselecting a wireless communication network in a black box according toan exemplary embodiment of the present invention.

FIG. 40 is a timing diagram illustrating a method for providing aconnected service according to an exemplary embodiment of the presentinvention.

FIG. 41 is a timing diagram illustrating a method for providing aconnected service according to another exemplary embodiment of thepresent invention.

FIG. 42 is a timing diagram illustrating a communication connectionprocess between a user terminal device and a black box according to anexemplary embodiment of the present invention.

FIG. 43 is a diagram illustrating a main user interface of a userterminal device according to another exemplary embodiment of the presentinvention.

FIGS. 44A to 44C are user interface diagrams illustrating an accountlogin process of a service subscriber according to an exemplaryembodiment of the present invention.

FIGS. 45A to 45C are user interface diagrams illustrating a process ofdisplaying a location of a vehicle according to an exemplary embodimentof the present invention.

FIGS. 46A to 46C are diagrams illustrating a process of setting whetherto notify geo-fencing according to an exemplary embodiment of thepresent invention.

FIGS. 47A to 47F are user interface diagrams illustrating a process ofsetting a geo-fencing area according to an exemplary embodiment of thepresent invention.

FIGS. 48A to 48C are user interface diagrams illustrating a process ofsetting a strong impact notification while driving a vehicle accordingto an exemplary embodiment of the present invention.

FIGS. 49A to 49C are user interface diagrams illustrating a process ofsetting an impact notification while parking a vehicle according to anembodiment of the present invention.

FIGS. 50A to 50C are user interface diagrams illustrating a process ofsetting a strong impact notification while parking a vehicle accordingto an exemplary embodiment of the present invention.

FIGS. 51A to 51E are diagrams illustrating a process of checking animpact image according to an exemplary embodiment of the presentinvention.

FIG. 52 is a table illustrating Auth Number field.

FIG. 53 is a table illustrating Play Type field.

FIG. 54 is a table illustrating Function Flag field.

FIG. 55 is a table illustrating ADAS Event field.

DETAILED DESCRIPTION

The following description merely illustrates the principles of thepresent invention. Therefore, those skilled in the art may implement theprinciple of the present invention and invent various devices includedin the spirit and scope of the present invention, although not clearlydescribed or illustrated in the present specification. In addition, itis to be understood that all conditional terms and exemplary embodimentsmentioned in the present specification are obviously intended only toallow those skilled in the art to understand a concept of the presentinvention in principle, and the present invention is not limited toexemplary embodiments and states particularly mentioned as such.

Further, it is to be understood that all detailed descriptionsmentioning specific exemplary embodiments of the present invention aswell as principles, aspects, and exemplary embodiments of the presentinvention are intended to include structural and functional equivalencesthereof. Further, it is to be understood that these equivalences includean equivalence that will be developed in the future as well as anequivalence that is currently well-known, that is, all elements inventedso as to perform the same function regardless of a structure.

Therefore, it is to be understood that, for example, a block diagram ofthe present specification shows a conceptual aspect of an illustrativecircuit for embodying the principle of the present invention. Similarly,it is to be understood that all flowcharts, state transition diagrams,pseudo-codes, and the like, illustrate various processes that may betangibly embodied in a computer readable medium and that are executed bycomputers or processors regardless of whether or not the computers orthe processors are clearly illustrated.

Functions of various elements including processors or functional blocksrepresented as concepts similar to the processors and illustrated in theaccompanying drawings may be provided using hardware having capabilityto execute appropriate software as well as dedicated hardware. When thefunctions are provided by the processors, the functions may be providedby a single dedicated processor, a single shared processor, or aplurality of individual processors and some thereof may be shared witheach other.

In addition, terms mentioned as a processor, a control, or a conceptsimilar to the processor or the control should not be interpreted toexclusively cite hardware having the capability to execute software, butshould be interpreted to implicitly include digital signal processor(DSP) hardware and a read only memory (ROM), a random access memory(RAM), and a non-volatile memory for storing software without beinglimited thereto. The above-mentioned terms may also include otherwell-known hardware.

In the claims of the present specification, components represented asmeans for performing functions mentioned in a detailed description areintended to include all methods for performing functions including alltypes of software including, for example, a combination of circuitelements performing these functions, firmware/micro codes, or the like,and are coupled to appropriate circuits for executing the software so asto execute these functions. It is to be understood that since functionsprovided by variously mentioned means are combined with each other andare combined with a scheme demanded by the claims in the inventionsdefined by the claims, any means capable of providing these functionsare equivalent to means recognized from the present specification.

The above-mentioned objects, features, and advantages will become moreobvious from the following detailed description provided in relation tothe accompanying drawings. Therefore, those skilled in the art to whichthe present invention pertains may easily practice a technical idea ofthe present invention. Further, in describing the present invention, inthe case in which it is judged that a detailed description of awell-known technology associated with the present invention mayunnecessarily make the gist of the present invention unclear, it will beomitted.

Hereinafter, various exemplary embodiments of the present invention willbe described in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram illustrating a connected service systemaccording to an exemplary embodiment of the present invention. Referringto FIG. 1 , a connected service system 1000 includes an image capturingapparatus 100 for a vehicle, a communication apparatus 200 for avehicle, a server 300 for providing a connected service, a user terminaldevice 400, and a base station 500.

In the present invention, the vehicle is an example of a moving body,and the moving body according to the present invention is not limited tothe vehicle. The moving body according to the present invention mayinclude various objects that may be moved, such as a vehicle, a person,a bicycle, a ship, and a train. Hereinafter, for convenience ofexplanation, a case in which the moving object is the vehicle will bedescribed as an example.

The base station 500 is a wireless communication facility that connectsa network and various terminals for a service of wireless communication,and enables communication between the image capturing apparatus 100 fora vehicle, the communication apparatus 200 for a vehicle, the server 300for providing a connected service, and the user terminal device 400included in the connected service system 1000 according to the presentinvention. As an example, the communication apparatus 200 for a vehiclemay be wirelessly connected to a communication network through the basestation 500, and if the communication apparatus 200 for a vehicle isconnected to the communication network, the communication apparatus 200for a vehicle may exchange data with other devices (e.g., the server 300for providing a connected service and the user terminal device 400)connected to the network.

The image capturing apparatus 100 for a vehicle may be provided in thevehicle to capture an image related to driving of the vehicle in adriving situation of the vehicle such as driving, stopping, and parkingof the vehicle (hereinafter, driving, stopping, and parking arecollectively referred to as driving), and store the captured image.

In addition, the image capturing apparatus 100 for a vehicle may becontrolled by a user control input through the user terminal device 400.For example, when the user selects an executable object installed on theuser terminal device 400, the image capturing apparatus 100 for avehicle may perform operations corresponding to an event generated by auser input to the executable object. Here, the executable object may bea type of application installed on the user terminal device 400 toremotely control the image capturing apparatus 100 for a vehicle.

In addition, in the present specification, an action that triggers theoperation of the image capturing apparatus 100 for a vehicle will bedefined as an event. For example, the types of events may be impactdetection, motion detection, user gesture detection, user touchdetection, and reception of a control command from a remote. Here, theimage capturing apparatus 100 for a vehicle may include all or some of afront capturing apparatus that captures the front of the vehicle, a rearcapturing apparatus that captures the rear thereof, aside capturingapparatus that captures the left and right sides thereof, a capturingapparatus that captures a face of a driver of the vehicle, and aninterior capturing apparatus that captures an interior of the vehicle.

In the present specification, an infra-red camera for a vehicle, ablack-box for a vehicle, a car dash cam, or a car video recorder aredifferent expressions of the image capturing apparatus 100 for avehicle, and may all mean the same.

The communication apparatus 200 for a vehicle is an apparatus that isconnected to the image capturing apparatus 100 for a vehicle to enablecommunication of the image capturing apparatus 100 for a vehicle, andthe image capturing apparatus 100 for a vehicle may communicate with anexternal server through the communication apparatus 200 for a vehicle.Here, the communication apparatus 200 for a vehicle may use variouswireless communication connection methods such as cellular mobilecommunication such as Long Term Evolution (LTE), and a wireless localarea network (WLAN) method such as Wireless Fidelity (WiFi).

In addition, according to an exemplary embodiment of the presentinvention, the communication apparatus 200 for a vehicle performingwireless communication with the server may be implemented as acommunication module using low-power wide-area (LPWA) technology. Here,as an example of the low-power wide-area technology, a low-powerwideband wireless communication module such as Long Range (LoRa), NarrowBand-Internet of Things (NB-IoT), or Cat M1 may be used.

Hereinafter, for convenience of explanation, a case in which thecommunication apparatus 200 for a vehicle is implemented as acommunication module using the low-power wide-area technology will bedescribed as an example. However, this is only an example ofimplementation of the present invention, and the example ofimplementation of the communication apparatus 200 for a vehicle is notlimited thereto, and the communication apparatus 200 for a vehicleaccording to the present invention may be implemented as anycommunication module that may communicate with external devices.

Meanwhile, the communication apparatus 200 for a vehicle according to anexemplary embodiment of the present invention may also perform alocation tracking function such as a global positioning system (GPS)tracker.

In addition, in FIG. 1 , the communication apparatus 200 for a vehicleis described as being an external type provided separately from theimage capturing apparatus 100 for a vehicle, but is not limited thereto,and the communication apparatus 200 for a vehicle may also beimplemented as a built-in communication module provided inside the imagecapturing apparatus 100 for a vehicle.

In the present specification, the dongle is another expression of thelow-power wide-area communication apparatus (or low-power wide-areacommunication module) or the communication apparatus 200 for a vehicle,and may all mean the same.

The server 300 for providing a connected service relays various databetween the communication apparatus 200 for a vehicle and the userterminal device 400 to enable various connected services to be describedlater.

As an example, the server 300 for providing a connected service mayreceive data including various information generated by the imagecapturing apparatus 100 for a vehicle from the communication apparatus200 for a vehicle, and store the received data by matching the receiveddata to user identification information. In addition, the server 300 forproviding a connected service may transmit the data generated by theimage capturing apparatus 100 for a vehicle to a user corresponding tothe user identification information. Here, the user corresponding to theuser identification information may mean a user with authority to data.

In this case, the user terminal device 400 may display a screenproviding a variety of meaningful information based on the receiveddata.

Here, the server 300 for providing a connected service may include amessage queuing telemetry transport (MQTT) server and a transmissioncontrol protocol (TCP) server from a viewpoint of a messaging protocol.

MQTT is a lightweight publish/subscribe-based messaging protocol, andmeans a protocol designed to be used in low power and low bandwidthenvironments for the Internet of Things (IoT). The MQTT server accordingto the present invention performs communication with the communicationapparatus 200 for a vehicle and the user terminal device 400 using theMQTT protocol, thereby enabling various connected services to bedescribed later.

TCP means a protocol used in a transport layer, which a fourth layer ofan OSI model developed as a communication standard. The TCP serveraccording to the present invention performs communication with thecommunication apparatus 200 for a vehicle and the user terminal device400 using the TCP protocol, thereby enabling various connected servicesto be described later.

The user terminal device 400 may be installed with an application(hereinafter, referred to as “connected service application”) fortransmitting and receiving various data to and from the image capturingapparatus 100 for a vehicle and/or the communication apparatus 200 for avehicle through the server 300 for providing a connected service anddisplaying the result. Accordingly, the user may execute the connectedservice application installed on the user terminal device 400, anddisplay a guide screen based on various data related to the drivingsituation of the vehicle received from the image capturing apparatus 100for a vehicle according to the execution of the application. Here, theuser terminal device 400 may be implemented as a smart phone, a tabletcomputer, a notebook computer, a personal digital assistant (PDA), or aportable multimedia player (PMP), or may also be implemented as awearable device such as a smart glass wearable on a user's body, a headmounted display (HMD), or the like.

Here, the user may be a person having management authority for thevehicle and/or the image capturing apparatus 100 for a vehicle such as avehicle owner, a vehicle driver, an owner of the image capturingapparatus 100 for a vehicle, or a supervisor of the image capturingapparatus 100 for a vehicle.

Hereinafter, the image capturing apparatus for a vehicle, the server forproviding a connected service, and the user terminal device according toan exemplary embodiment of the present invention will be described inmore detail with reference to the subsequent drawings.

FIG. 2 is a block diagram illustrating the image capturing apparatus fora vehicle according to an exemplary embodiment of the present invention.Referring to FIG. 2 , the image capturing apparatus 100 for a vehiclemay include a capturing unit 110, a user input unit 120, a microphoneunit 130, a display unit 140, an audio unit 150, a storage unit 160, animpact detection unit 170, a vehicle driving support function unit 180,a communication unit 190, and a control unit 195.

The capturing unit 110 may capture a driving image of the vehicle. Here,the driving image of the vehicle is an image captured in at least onesituation of parking, stopping, and driving of the vehicle, and mayinclude at least one image of the front, rear, side, and interior of thevehicle. At this time, the capturing unit 110 may also include aninfrared camera that may monitor a face or a pupil of a driver, and thecontrol unit 195 may determine a driver's state including whether thedriver is drowsy or not by monitoring the face or the pupil of thedriver through an infrared camera.

The capturing unit 110 may include a lens unit and an imaging element.The lens unit may perform a function of condensing an optical signal,and the optical signal transmitted through the lens unit 21 reaches animaging area of the imaging element and forms an optical image. Here, asthe imaging element, a charge coupled device (CCD), a complementarymetal oxide semiconductor image sensor (CIS), a high speed image sensor,or the like that converts the optical signal into an electrical signalmay be used. In addition, the capturing unit 110 may further include allor some of a lens unit driving unit, an aperture, an aperture drivingunit, an imaging element control unit, and an image processor.

The user input unit 120 is a component that receives various user inputsfor operating the image capturing apparatus 100 for a vehicle, and mayreceive, for example, a user input for setting an operation mode of theimage capturing apparatus 100 for a vehicle, a user input for displayinga recorded image on the display unit 140, a user input for setting amanual recording, and the like.

Here, the operation mode of the image capturing apparatus 100 foravehicle may include a normal recording mode, an event recording mode, amanual recording mode, and a parking recording mode.

The normal recording mode is a mode that is executed when an engine ofvehicle is turned on and the vehicle starts driving, and the normalrecording mode may be maintained while the vehicle continues to drive.In the normal recording mode, the image capturing apparatus 100 for avehicle may perform recording in a predetermined time unit (e.g., 1 to 5minutes). In the present invention, the normal recording mode and thenormal mode may be used in the same sense.

The parking recording mode may refer to a mode in which the engine ofvehicle is turned off or a battery supply for driving of the vehicle isstopped to operate in a parked state. In the parking recording mode, theimage capturing apparatus 100 for a vehicle may perform recording duringa certain period (for example, recording before 10 seconds to after 10seconds of an occurrence of an event) from a predetermined time of theoccurrence of an impact event to a predetermined time after theoccurrence of the impact event. In the present invention, the parkingrecording mode and the parking mode may be used in the same sense.

The event recording mode may refer to a mode operated when an impactevent is detected by the impact detection unit 170 or an advanceddriving assistance system (ADAS) event is detected by the vehicledriving support function unit 180 while driving the vehicle. In theevent recording mode, the image capturing apparatus 100 for a vehiclemay perform recording during a time (for example, recording before 10seconds to after 10 seconds of an occurrence of an event) from apredetermined time before the occurrence of the event to a predeterminedtime after the occurrence of the event.

The manual recording mode may refer to a mode operated by a usermanually inputting recording. In the manual recording mode, the imagecapturing apparatus 100 for a vehicle may perform recording during atime (for example, recording before 10 seconds to after 10 seconds of anoccurrence of an event) from a predetermined time before an occurrenceof a manual recording request of the user to a predetermined time afterthe occurrence of the manual recording request of the user.

Here, the user input unit 120 may be configured in various ways that mayreceive a user input, such as a key pad, a dome switch, a touch pad, ajog wheel, and a jog switch.

The microphone unit 130 may receive a sound generated from the inside oroutside of the vehicle or a voice according to a user's speech. Here,the received voice or sound may be related to a sound caused by anexternal impact or a situation inside/outside the vehicle, and may helpto recognize a situation at the time together with an image captured bythe capturing unit 110.

The display unit 140 may display a variety of information processed bythe image capturing apparatus 100 for a vehicle. For example, thedisplay unit may display a “live view image” which is an image capturedin real time by the capturing unit 110, and may display a setting screenfor setting an operation mode of the image capturing apparatus 100 for avehicle.

The audio unit 150 may output audio data received from an externaldevice or stored in the storage unit 160. Here, the audio unit 150 maybe implemented as a speaker that outputs the audio data.

The storage unit 160 stores various data and programs necessary for theoperation of the image capturing apparatus 100 for a vehicle. Inparticular, the storage unit 160 may store a driving image captured bythe capturing unit 110 and voice data input through the microphone unit130.

In addition, the storage unit 160 may classify and store data obtainedaccording to the operation mode of the image capturing apparatus 100 fora vehicle in different storage areas.

The storage unit 160 may be configured inside the image capturingapparatus 100 for vehicle, or configured detachably through a portprovided in the image capturing apparatus 100 for a vehicle, or mayexist outside the image capturing apparatus 100 for a vehicle. When thestorage unit 160 is configured inside the image capturing apparatus 100for a vehicle, the storage unit 160 may exist in the form of a hard diskdrive or flash memory. When the storage unit 160 is configureddetachably in the image capturing apparatus 100 for a vehicle, thestorage unit 160 may exist in the form of an SD card, a Micro SD card, aUSB memory, or the like. When the storage unit 160 is configured outsidethe image capturing apparatus 100 for a vehicle, the storage unit 160may exist in a storage space in another device or a database serverthrough the communication unit 190.

The impact detection unit 170 may detect an impact applied to thevehicle or a case in which a change in acceleration is a certain amountor more. Here, the impact detection unit 170 may include an accelerationsensor, a geomagnetic sensor, and the like to detect impact oracceleration.

The vehicle driving support function unit 180 may determine whether ornot a driving support function is required for the driver of the vehiclebased on the driving image captured by the capturing unit 110.

As an example, the vehicle driving support function unit 180 may detecta start of a vehicle located in front of the vehicle and determinewhether or not a forward vehicle start alarm (FVSA) is required for thedriver, based on the driving image captured by the capturing unit 110.If a predetermined time has elapsed after the forward vehicle started,the vehicle driving support function unit 180 may determine that theforward vehicle start alarm is required.

In addition, the vehicle driving support function unit 180 may detectwhether or not a signal is changed and determine whether or not atraffic light change alarm (TLCA) is required for the driver, based onthe driving image captured by the capturing unit 110. As an example, ifa stop state (0 km/h) is maintained for 4 seconds in a state in whichthe signal is changed from a stop signal to a straight signal, thevehicle driving support function unit 180 may determine that the trafficlight change alarm is required.

In addition, the vehicle driving support function unit 180 may detectwhether or not the vehicle departures from a lane and determine a lanedeparture warning system (LDWS) is required for the driver, based on thedriving image captured by the capturing unit 110. As an example, whenthe vehicle departs from the lane, the vehicle driving support functionunit 180 may determine that the lane departure warning system isrequired.

In addition, the vehicle driving support function unit 180 may detect adanger of a collision a vehicle in front of the vehicle and determine aforward collision warning system (FCWS) is required for the driver,based on the driving image captured by the capturing unit 110. As anexample, the vehicle driving support function unit 180 may determinethat a primary forward collision warning system is required when aninitial forward collision danger is detected, and determine that asecondary forward collision warning system is required when an intervalwith the front vehicle is further reduced after the initial forwardcollision danger is detected.

Here, the forward collision warning system may further include an urbanFCWS (uFCWS) that provides a forward collision warning at a lowerdriving speed so as to be suitable for an environment in which a drivingspeed is low.

The communication unit 190 may enable the image capturing apparatus 100for a vehicle to communicate with other devices, where the communicationunit 190 may be implemented as the low-power wide-area communicationapparatus 200 described above. Accordingly, the image capturingapparatus 100 for a vehicle may communicate with the server 300 forproviding a connected service and/or the user terminal device 400through the communication unit 190. In addition, the communication unit190 may be directly connected to the user terminal device 400, such asWiFi Direct.

Hereinafter, for convenience of explanation, a case in which thecommunication unit 190 is separately provided as the communicationapparatus 200 for a vehicle will be described as an example.

The control unit 195 controls an overall operation of the imagecapturing apparatus 100 for a vehicle. Specifically, the control unit195 may control all or some of the capturing unit 110, the user inputunit 120, the microphone unit 130, the display unit 140, the audio unit150, the storage unit 160, the impact detection unit 170, the vehicledriving support function unit 180, and the communication unit 190.

In particular, the control unit 195 may set the operation mode of theimage capturing apparatus 100 for a vehicle to one of the normalrecording mode, the event recording mode, the parking recording mode,and the manual recording mode, based on at least one of whether or notthe vehicle is started, a measurement result of the battery voltage ofthe vehicle, a detection result of the impact detection unit 170, adetermination result of the vehicle driving support function unit 180,and a set value of the operation mode. In addition, the control unit 195may perform control to stop the operation of the image capturingapparatus 100 for a vehicle when the battery voltage of the vehiclefalls below a threshold value or less.

In addition, the control unit 195 may generate data illustrated in FIGS.5 to 11 to be described later based on various collected data. As anexample, when the impact detection unit 170 detects an impact or amovement of the vehicle while parking or driving the vehicle, it ispossible to generate impact event data, extract at least two imagesamong images captured within a predetermined time range of eventoccurrence, and generate image upload data using the extracted images.Here, the movement of the vehicle may refer to a situation in whichtowing of the vehicle is performed.

As another example, the control unit 195 may generate event datacorresponding to a parking location image request response event or alive image request response event, respectively, according to a requestfrom the user terminal device receiving the connected service, andextract images at a time point corresponding to the events to generatean image upload data.

As another example, the control unit 195 may generate ADAS event datawhen it is determined that a driving support function is required forthe vehicle driving support function unit 180. Here, the ADAS event datamay include an event type indicating an ADAS event type, an eventoccurrence time, and an event occurrence location.

As another example, the control unit 195 may perform control to adjust asize of data to be transmitted to the server 300 in consideration of adata communication speed with the server 300 for providing a connectedservice, a state of the battery of the image capturing apparatus for avehicle, a size of a user storage space allocated to the server 300 forproviding a connected service, and the like.

Meanwhile, the control unit 195 may transmit the generated data to theserver 300 for providing a connected service through the low-powerwide-area communication module. Here, the data transmitted to the server300 for providing a connected service may be used to provide a connectedservice to be described later.

FIG. 3 is a block diagram illustrating a user terminal device accordingto an exemplary embodiment of the present invention. Referring to FIG. 3, the user terminal device 400 may include all or some of acommunication unit 410, a storage unit 420, an input unit, an outputunit 440, and a control unit 450.

The communication unit 410 may be provided in order for the userterminal device 400 to communicate with other devices. Specifically, theuser terminal device 400 may transmit and receive data to and from atleast one of the image capturing apparatus 100 for a vehicle, thecommunication apparatus 200 for a vehicle, and the server 300 forproviding a connected service.

Here, the communication unit 410 may be implemented using variouscommunication schemes such as a connection form in a wireless or wiredscheme through a local area network (LAN) and the Internet network, aconnection form through a universal serial bus (USB) port, a connectionform through a mobile communication network such as the 3G and 4G mobilecommunication networks, and a connection form through a short rangewireless communication scheme such as near field communication (NFC),radio frequency identification (RFID), Wi-Fi, or the like.

The storage unit 420 serves to store various data and applicationsrequired for an operation of the user terminal device 400. Inparticular, the storage unit 420 may store a “connected serviceapplication” according to an exemplary embodiment of the presentinvention.

Here, the storage unit 420 may be implemented as a detachable type ofstorage element such as a USB memory, as well as an embedded type ofstorage element such as a random access memory (RAM), a flash memory, aread only memory (ROM), an erasable programmable ROM (EPROM), anelectronically erasable and programmable ROM (EEPROM), a register, ahard disk, a removable disk, a memory card, or a universal subscriberidentity module (USIM).

The input unit 430 serves to convert a physical input from the outsideof the user terminal device 400 into a specific electrical signal. Here,the input unit 430 may include all or some of a user input unit and amicrophone unit.

The user input unit may receive a user input such as a touch, a gesture,or a push operation. Here, the user input unit may be implemented invarious types of buttons, a touch sensor receiving a touch input, and aproximity sensor receiving an approaching motion. In addition, themicrophone unit may receive a voice of the user and a sound generatedfrom the inside and the outside of the vehicle.

The output unit 440 is a component that outputs data of the userterminal device 400, and the output unit 440 may include a display unit441 and an audio output unit 443.

The display unit 441 may output data visually recognizable by the userof the user terminal device 400. In particular, the display unit 441 maydisplay a connected service user interface according to execution of the“connected service application” according to an exemplary embodiment ofthe present invention.

Here, the connected service user interface may include various userinterfaces such as a “main user interface that aggregates and displaysvarious information that is helpful to the user”, a “last parkinglocation guide user interface”, a “live image display user interface”, a“remote image playback user interface”, a “coupon service userinterface”, and an “emergency SOS user interface”. The various userinterfaces will be described later with reference to FIGS. 12 to 37 .

Meanwhile, the audio output unit 443 may output data auditorilyrecognizable by the user of the user terminal device 400. Here, theaudio output unit 443 may be implemented as a speaker that expressesdata to be notified to the user of the user terminal device 400 assound.

The control unit 450 controls an overall operation of the user terminaldevice 400. Specifically, the control unit 450 may control all or someof the communication unit 410, the storage unit 420, the input unit 430,and the output unit 440. In particular, if various data is received fromthe image capturing apparatus 100 for a vehicle, the communicationapparatus 200 for a vehicle, and/or the server 300 for providing aconnected service through the communication unit 410, the control unit450 may process the received data to generate a user interface, andcontrol the display unit 441 to display the generated user interface.

The control unit 450 may execute applications that provideadvertisements, the Internet, games, videos, and the like. In variousexemplary embodiments, the control unit 450 may include one processorcore (single core) or include a plurality of processor cores. Forexample, the control unit 450 may include a multi-core such as adual-core, a quad-core, and a hexa-core. According to exemplaryembodiments, the control unit 450 may further include a cache memorylocated internally or externally.

The control unit 450 may receive commands of other components of theuser terminal device 400, interpret the received commands, and performcalculation or process data according to the interpreted commands.

The control unit 450 may process data or signals generated or occurringin an application. For example, the control unit 450 may requestinstructions, data, or signals to the storage unit 420 to execute orcontrol the application. The control unit 450 may write (or store) orupdate the instructions, the data, or the signals in the storage unit420 to execute or control the application.

The control unit 450 may interpret and process messages, data,instructions, or signals received from the communication unit 410, thestorage unit 420, the input unit 430, and the output unit 440. Inaddition, the control unit 450 may generate new messages, data,instructions, or signals based on the received messages, data,instructions, or signals. The control unit 450 may provide the processedor generated messages, data, instructions, or signals to thecommunication unit 410, the storage unit 420, the input unit 430, theoutput unit 440, and the like.

All or part of the control unit 450 may be electrically or operablycoupled with or connected to other components (e.g., the communicationunit 410, the storage unit 420, the input unit 430, and the output unit440) in the user terminal device 400.

According to exemplary embodiments, the control unit 450 may include oneor more processors. For example, the control unit 450 may include anapplication processor (AP) for controlling a program of an upper layersuch as an application program, a communication processor (CP) forperforming a control for communication, or the like.

Meanwhile, the above-described input unit 430 may receive aninstruction, interaction, or data from the user. The input unit 430 maysense a touch or hovering input of a finger and a pen. The input unit430 may sense an input caused through a rotatable structure or aphysical button. The input unit 430 may include sensors for sensingvarious types of inputs. The input received by the input unit 430 mayhave various types. For example, the input received by the input unit430 may include a touch and release, a drag and drop, a long touch, aforce touch, a physical depression, and the like. The input unit 430 mayprovide the received input and data related to the received input to thecontrol unit 450. In various exemplary embodiments, although notillustrated in FIG. 3 , the input unit 430 may include a microphone (ortransducer) capable of receiving a user's voice command. In variousexemplary embodiments, although not illustrated in FIG. 3 , the inputunit 430 may include an image sensor or a camera capable of receiving auser's motion.

Meanwhile, the above-described display unit 441 may output content,data, or signals. In various exemplary embodiments, the display unit 441may display an image signal processed by the control unit 450. Forexample, the display unit 441 may display a capture or still image. Asanother example, the display unit 441 may display a video or a camerapreview image. As another example, the display unit 441 may display agraphical user interface (GUI) so that the user may interact with theterminal device 400.

The display unit 441 may be configured with a liquid crystal display(LCD) or an organic light emitting diode (OLED).

According to exemplary embodiments, the display unit 441 may beconfigured with an integrated touch screen by being coupled with asensor capable of receiving a touch input or the like.

In various exemplary embodiments, the control unit 450 may map at leastone function to the input unit 430 such that the input unit 430 has atleast one function among a plurality of functions that the user terminaldevice 400 may provide to the user. For example, the at least onefunction may include at least one of an application execution function,a vehicle's last parking location display function, a parking locationguide function, a my driving record notification function, a live viewviewing function, which is a real-time capturing image viewing functionof the black box 100, a power on/off control function of the black box100, a power on/off function of the vehicle, a function related toweather, a driving time guide function, a fuel efficiency guidefunction, a vehicle's parking/driving mode guide function, a vehicledriving information guide function, an event occurrence guide function,a vehicle's current location inquiry function, a vehicle's parkinglocation and parking time guide function, a parking history guidefunction, a driving history guide function, an image sharing function,an event history function, a remote playback function, and an imageviewing function.

In various exemplary embodiments, the input unit 430 may receive theconfiguration information from the control unit 450. The input unit 430may display indications for indicating the functions based on theconfiguration information.

For example, referring to FIGS. 11 to 36 to be described later, theinput unit 430 may display various indications as visual objects basedon the configuration information received from the control unit 450.

In various exemplary embodiments, the control unit 450 may transmit theconfiguration information to the input unit 430 to indicate what the atleast one function mapped to the input unit 430 is. The configurationinformation may include data for displaying, through the display unit441, an indication for indicating which function of the plurality offunctions is provided through the input unit 430. The configurationinformation may include data for indicating a function selected by thecontrol unit 450 among the plurality of functions.

FIG. 4 is a block diagram illustrating a server for providing aconnected service according to an exemplary embodiment of the presentinvention. Referring to FIG. 4 , the server 300 for providing aconnected service may include a communication unit 310, a storage unit320, and a control unit 330.

The communication unit 310 may be provided in order for the server 300for providing a connected service to communicate with other devices.Specifically, the communication unit 310 may transmit and receive datato and from at least one of the image capturing apparatus 100 for avehicle, the communication apparatus 200 for a vehicle, and the userterminal device 400. Here, the communication unit 310 may be implementedas various well-known communication modules.

The storage unit 320 may store various data and programs for anoperation of the server 300 for providing a connected service. Here, thestorage unit 320 may include a service subscription information storageunit 321 and a service operation information storage unit 322.

Specifically, when a user who wants to receive a connected servicesubscribes to the service as a member using own terminal device 400, theservice subscription information storage unit 321 may store servicesubscription information generated based on the information inputthrough the member subscription. Here, the service subscriptioninformation storage unit 321 may store subscriber information subscribedto the connected service as the member and device information of thecorresponding subscriber. The subscriber information may includesubscriber identification information and subscription serviceinformation.

The subscription service information is information indicating in detailthe service to which the subscriber has subscribed, and may include aservice application history, a rate plan, a service expiration date, adata rate, a service type, and the like.

The subscriber identification information is information that enablesidentification of each of a plurality of subscribers, and may include asubscriber's ID, a subscriber's password, a subscriber's social securitynumber, a subscriber's name, a subscriber's nickname, a subscriber'spersonal identification number (PIN), and the like.

In addition, the subscriber device information may include at least oneof identification information of the image capturing apparatus 100 for avehicle and identification information of the communication apparatus200 for a vehicle purchased by the subscriber. Here, the identificationinformation of the image capturing apparatus 100 for a vehicle isinformation that enables identification of each of a plurality of imagecapturing apparatuses for a vehicle, and may include a black box modelname, a black box unique serial number, and the like. In addition, theidentification information of the communication apparatus 200 for avehicle is information that enables identification of each of aplurality of communication apparatuses for a vehicle, and may include adongle model name, a dongle phone number, a dongle serial number, auniversal subscriber identity module (USIM) serial number, and the like.

In addition, the subscriber device information may further includeidentification information of the terminal device 400 of the subscriber,and the identification information of the user terminal device 400 mayinclude international mobile subscriber identity (IMSI), integratedcircuit card ID (ICCID), and international mobile equipment identity(IMEI), which are the unique information given by the network toidentify the user terminal device 400.

In this case, the service subscription information storage unit 321 maymatch and store the subscriber information and the subscriber deviceinformation for each subscriber subscribed to the service as the member.

On the other hand, when the user who subscribes to the service receivesthe connected service based on the data generated by the image capturingapparatus 100 for a vehicle, the service operation information storageunit 322 may store various data generated in a connected serviceoperation process. As an example, the service operation informationstorage unit 322 may store various data generated in the connectedservice operation process as illustrated in Tables 1 to 49, which willbe described later.

As an example, when various events such as a vehicle's impact detection,a vehicle's battery off detection, and a live image request from theuser terminal device occur, the image capturing apparatus 100 for avehicle may generate corresponding event data and transmit the generatedevent data to the server 300 through the communication apparatus 200 fora vehicle. In this case, the service operation information storage unit322 may match and store the received event data to the servicesubscription information corresponding to the image capturing apparatus100 for a vehicle.

Here, the storage unit 320 may be implemented as an embedded module ofthe server 300 or may be implemented as a separate database (DB) server.

Meanwhile, the control unit 330 may control the overall operation of theserver 300 for providing a connected service so that the connectedservice according to the present invention is provided.

The operation of the server 300 for providing a connected service may bedivided into a “new subscription process” in which the user newlysubscribes to a service and a “connected service provision process” inwhich the connected service is provided to a subscriber who subscribesto the service.

In the “new subscription process”, the control unit 330 may performcontrol to initiate a service subscription procedure when a servicemember subscription is requested from the subscriber, acquire thesubscriber information subscribed to the connected service as the memberand the device information of the corresponding subscriber, and classifyand store the acquired information. Accordingly, the storage unit 320may establish a subscriber information database.

In the “connected service provision process”, the control unit 330 maycontrol various processes such as a black box/user registration process,an event registration process, and an image registration/upload processillustrated in FIGS. 5 to 11 to be described later to provide theconnected service to the user terminal device 400. As an example of theconnected service provision, the user terminal device 400 may displayuser interfaces that provide various information related to the vehicleas illustrated in FIGS. 12 to 37 .

As an example, when the “registration process of the black box” isperformed, the control unit 330 may receive unique information foridentifying a communication apparatus such as a universal subscriberidentity module (USIM) chip embedded in the communication apparatus 200for a vehicle through communication with the communication apparatus 200for a vehicle, and may compare the unique information with informationpreviously stored in the storage unit 320 to check validity of thecommunication apparatus 200 that has requested registration.

Similarly, in the “registration process of the user”, when the userterminal device 400 accesses the server 300, the control unit 330 mayacquire user identification information such as the USIM embedded in theuser terminal device 400 and may then compare the information previouslystored in the storage unit 320 with the acquired user identificationinformation to check whether the user terminal device 400 subscribes tothe service and the type of service. If authentication for the user issuccessfully completed, the control unit 330 may provide variousinformation about the image capturing apparatus 100 for a vehicle invarious UX forms based on an authority assigned to the user.

As another example, when the “image registration/upload process” isperformed, the control unit 330 may receive an image captured from theimage capturing apparatus 100 for a vehicle, and notify the userterminal device 400 of the completion of the image upload when uploadingof the received image is completed.

More specifically, the control unit 330 may notify the user terminaldevice 400 in the form of a push message a message indicating that theupload of the received image is completed, and in this case, the userterminal device 400 may display the completion of the image upload in apop-up form to the user through the display unit. If the user clicks thedisplayed pop-up message, the user terminal device 400 may download theimage uploaded to the server 300 and display the downloaded image to theuser.

Hereinafter, an operation of the connected service system 1000 and aninterworking protocol between the communication apparatus 200 for avehicle and the server 300 for providing a connected service will bedescribed in more detail with reference to FIGS. 5 to 11 .

Here, the black box/user registration process, the event registrationprocess, and the image registration/upload process illustrated in FIGS.5 to 11 may be processes after the user subscribes to the connectedservice according to the present invention through a membersubscription.

In addition, in FIGS. 5 to 11 , the black box may refer to the imagecapturing apparatus 100 for a vehicle, and the dongle may refer to thecommunication apparatus 200 for a vehicle.

FIG. 5 is a timing diagram illustrating an operation scenario of aconnected service system in black box registration and user registrationprocesses according to the present invention. The black box/userregistration process according to FIG. 5 is a procedure performed beforeproviding the connected service to the user who subscribes to theservice, and may be performed whenever the power of the black box isturned on. As an example, when the power is applied to the black box byturning on the engine of the vehicle in a state in which the black boxis turned off, the black box/user registration process may be performedwhenever the power of the black box is turned on, such as when the powerof the black box is turned on again after a forced termination of theblack box.

Referring to FIG. 5 , first, the vehicle 10 may apply power to the blackbox 100 (S11), the black box 100 may apply the power to the dongle 200(S12), the dongle 200 may transmit an attach request to the base station500 (S13), and the base station 500 may transmit an attach accept to thedongle 200 (S14).

Then, when the dongle 200 accesses the network through low-powerwide-area communication, the dongle 200 may receive assisted GPS (A-GPS)information from the base station 500 (S15). The black box 100 maycalculate a location of the vehicle 10 using the A-GPS informationreceived through the dongle 200. In addition, a domain name system (DNS)query may be shared between the dongle 200 and the base station 500(S16).

On the other hand, when the dongle 200 accesses the communicationnetwork through the base station 500 according to the above-describedprocess, the black box 100 may transmit a terminal registration requestincluding terminal data (AT$BBINFO) to the dongle 200 (S17), the dongle200 may transmit the terminal registration request to a TCP server 302,and the TCP server 302 may transmit a terminal registration response,which is a response to the terminal registration request, to the dongle200 (S18). Here, the terminal registration request may be a request forregistering with the service before providing the connected service tothe black box 100 and/or dongle 200 subscribed to the service.

Here, the terminal registration request transmitted from the dongle 200to the TCP server 302 may be configured in a data format illustrated inTable 1 below.

TABLE 1 Description cat.m1 Dongle & Black Box Registration RequestDirection Client −> Server No. Offset Byte Type Contents DescriptionValue Endian 1 0 2 byte[ ] STX Packet Start 0x02 0x0E 2 2 1 unsignedPacket 0x31 char Type 3 3 1 unsigned Total No. 4~No. 11 char LengthLength 4 4 19+ string BBOX Name Black Box Model Name 5 23 1 charDivision Separator 0xFF 6 24 8 string Dongle Dongle Model Name Name 7 321 char Division Separator 0xFF 8 33 8 string Dongle Dongle VersionVersion 9 41 1 char Division Separator 0xFF 10 42 11  string DongleDongle Phone CTN Number 11 53 1 char Division Separator 0xFF 12 54 2byte[ ] ETX Packet End 0x03 0x0F Total Len 56+

Among the contents of Table 1, the BBOX Name field is a field thatincludes the model name of the black box, which is the image capturingapparatus for a vehicle, and version information of the model, and adescription thereof is illustrated in Table 2 below.

TABLE 2 Field Description BBOX Name Black Box Model Name + Version(Separated by Parentheses (‘(‘/’)’)) − ex> QUANTUM2X(v1.01.00)

In addition, the terminal registration response transmitted from the TCPserver 302 to the dongle 200 may be configured in a data formatillustrated in Table 3 below.

TABLE 3 Description cat.m1 Dongle & Black Box Registration RequestResponse Direction Server −> Client No. Offset Byte Type ContentsDescription Value Endian 1 0 2 byte[ ] STX Packet Start 0x02 0x0E 2 2 1unsigned Packet 0x52 char Type 3 3 1 unsigned Total No. 4~No. 14 charLength Length 4 4 2 unsigned Code Server Little short Response Code 5 64 unsigned uuid Terminal Little in Unique Number 6 10  15+ string A-GPSURL 7 25+ 1 char Division Separator 0xFF 8 26+ 2 unsigned A-GPS Littleshort Port 9 28+ 2 unsigned Traffic Traffic minute Little short Day ProInformation Day Use 10 30+ 1 unsigned Traffic Traffic second char GatherInformation Gather Period 11 31+ 1 unsigned Traffic Traffic second charReport Information Transmission Period 12 32+ 1 unsigned Park ImgParking char Cnt. Image Count 13 33+ 1 unsigned Live Img Live Image charCnt. Count 14 34+ 1 unsigned Impact Impact Image char Img Cnt Count 1535+ 2 byte[ ] ETX Packet End 0x03 0x0F Total Len 37+

The description of A-GPS URL, A-GPS Port, Traffic Day Pro, TrafficGather, Traffic Report, Park Img Cnt., Live Img Cnt, Impact Img Cnt, andBBOX Name fields among the contents of Table 3 above is illustrated inTable 4 below.

TABLE 4 Field Description A-GPS URL Used When A-GPS IP Is Changed Later(Default : supl.google.com) A-GPS Port Used When A-GPS Port Is ChangedLater (Default : 7276) Traffic Traffic Information Day Use Time Limit(Default : Day Pro 720) Traffic Traffic Information Gather Period(Default :1) Gather Traffic Traffic Information Transmission PeriodReport (Default :2) Park Img Parking Image Remaining Count Cnt. Live ImgLive Image Remaining Count Cnt. Impact Img Impact Image Remaining CountCnt

That is, in order to reduce data usage in consideration of thecharacteristics of low-power wideband wireless communication, theresponse to the terminal registration request at the time of initialaccess may include the data fields capable of managing data usage, suchas traffic information day use time limit (Traffic Day Pro), trafficinformation gather period (Traffic Gather), traffic informationtransmission period (Traffic Report), parking image remaining count(Park Img Cnt), and live image remaining count (Live Img Cnt).

Meanwhile, the registration of the black box 100 and/or the dongle 200may be completed according to the process described above.

Thereafter, the black box 100 may transmit an MQTT server connectionrequest including terminal configuration data (AT$BBCFG) to the dongle200 (S19). In this case, the dongle 200 may transmit and receive aconnection request (CONNECT) and a connection response (CONNECT ACK) toand from the MQTT server 301 (S20).

Here, the connection request (CONNECT) from the dongle 200 to the MQTTserver 301 may be configured as a protocol as illustrated in Table 5below.

TABLE 5 Type bit 7 6 5 4 3 2 1 0 Fixed byte 1 Message Type (1) Reservedheader byte 2 Remaining length (Variable header + Payload) Variable byte1 Length MSB header byte 2 Length LSB byte 3 “M” byte 4 “Q” byte 5 “T”byte 6 “T” byte 7 Level (4) byte 8 User Password Will Will Will CleanReserved Name Flag Retain Qos Flag Session Flag 1 1 0 0 0 0 1 0 byte 9Keep Alive MSB byte 10 Keep Alive LSB payload byte 1 Client ID LengthMSB byte 2 Client ID Length LSB byte 3.N Client ID byte 1 User NameLength MSB (User Name Flag) byte 2 User Name Length LSB (User Name Flag)byte 3.N User Name (User Name Flag) byte 1 Password Length MSB (PasswordFlag) byte 2 Password Length LSB (Password Flag) byte 3.N Password(Password Flag)

In addition, the connection response (CONNECT ACK) transmitted from theMQTT server 301 to the dongle 200 may be configured as a protocol asillustrated in Table 6 below.

TABLE 6 Type bit 7 6 5 4 3 2 1 0 Fixed byte 1 Message Type (2) Reservedheader byte 2 Remaining length (Variable header) Variable byte 1Reserved SP header Flag (0) byte 2 Return Code

Thereafter, the communication apparatus 200 for a vehicle may transmitand receive a subscription request (SUBSCRIBE) and a subscriptionresponse (SUBSCRIBE ACK) to and from the MQTT server 301 (S21).

Here, the subscription request (SUBSCRIBE) from the dongle 200 to theMQTT server 301 may be configured as a protocol as illustrated in Table7 below.

TABLE 7 Type bit 7 6 5 4 3 2 1 0 Fixed byte 1 Message Type DUP QosRETAIN header (8) (0) (1) (0) byte 2 Remaining length (Variable header +Payload) Variable byte 1 Packet ID MSB header byte 2 Packet ID LSBpayload byte 1 Topic Filter Length MSB byte 2 Topic Filter Length LSBbyte Topic Filter 3.N byte Reserved Qos N + 1

In addition, the subscription response (SUBSCRIBE ACK) transmitted fromthe MQTT server 301 to the dongle 200 may be configured as a protocol asillustrated in Table 8 below.

TABLE 8 Type bit 7 6 5 4 3 2 1 0 Fixed byte 1 Message Type (9) Reservedheader byte 2 Remaining length (Variable header + Payload) Variable byte1 Packet ID MSB header byte 2 Packet ID LSB payload byte 1 Return code

Thereafter, the communication apparatus 200 for a vehicle may transmitand receive a publish request (PUBLISH) and a publish response (PUBLISHACK) to and from the MQTT server 301 (S22).

Here, the publish request (PUBLISH) from the dongle 200 to the MQTTserver 301 may be configured as a protocol as illustrated in Table 9below.

TABLE 9 Type bit 7 6 5 4 3 2 1 0 Fixed byte 1 Message Type (3) DUP Qos(1) RETAIN (0) header byte 2 Remaining length (Variable header +Payload) Variable byte 1 Topic Name Length MSB header byte 2 Topic NameLength LSB byte 3.N Topic Name byte N + 1 Packet ID MSB byte N + 2Packet ID LSB payload byte N Application Message

In addition, the publish response (PUBLISH ACK) transmitted from theMQTT server 301 to the dongle 200 may be configured as a protocol asillustrated in Table 10 below.

TABLE 10 Type bit 7 6 5 4 3 2 1 0 Fixed byte 1 Message Type (4) Reservedheader byte 2 Remaining length (Variable header + Payload) Variable byte1 Packet ID MSB header byte 2 Packet ID LSB

Thereafter, the user terminal device 400 may transmit a userregistration and authentication request to the MQTT server 301 (S23),and the dongle 200 may transmit and receive the publish request(PUBLISH) and the publish response (PUBLISH ACK) to and from the MQTTserver 301 (S24). Here, the user registration and authentication requestmay be a procedure for registering and authenticating the user beforeproviding the connected service to the user subscribed to the service.

In addition, the dongle 200 may transmit a user registration andauthentication request ($BBAUTHREQ) to the black box 100 (S25).

In this case, the black box 100 may transmit a user registration andauthentication success response (AT@BBAUTH=1) to the dongle 200 (S26),and the dongle 200 may transmit and receive the publish request(PUBLISH) and the publish response (PUBLISH ACK) to and from the MQTTserver 301 (S27).

Then, the MQTT server 301 may transmit that the user registration andauthentication is successful to the user terminal device 400 (S28).

Here, the protocols of the publish request (PUBLISH) and the publishresponse (PUBLISH ACK) of S24 and S27 may be as illustrated in Tables 9to 10 described above.

According to the processes of FIG. 5 described above, the registrationof the black box 100 and/or the dongle 200 as the power of the black boxis turned on may be performed, and the user registration andauthentication may be performed.

FIG. 6 is a timing diagram illustrating an operation scenario of aconnected service system in an event registration process according toan exemplary embodiment of the present invention. Referring to FIG. 6 ,first, the black box 100 may notify the dongle 200 of an eventregistration request including an event occurrence notification andevent data (“AT$BBEVT=1”) (S31). Here, the event may include variousevents such as an event that may occur in a driving situation of thevehicle, an event that may occur during the operation process of theblack box 100, and an event according to a request from the userterminal device 400. As an example, as illustrated in Table 15 below,the event according to the present invention may include various eventssuch as an impact event, a black box power off event, a black box lowvoltage occurrence event, and a black box authentication completionevent.

In this case, the communication apparatus 200 for a vehicle may transmitand receive a publish request (PUBLISH) and a publish response (PUBLISHACK) for event registration the event to and from the MQTT server 301(S22).

Here, a data format of MQTT PUBLISH of the publish request (PUBLISH) forevent registration may be as illustrated in Tables 11 and 12 below.

TABLE 11 Description Transmit Status Information from Cat.M1 Dongle toServer (Parking or Not, Impact or Not, Latitude, Longitude) DirectionClient −> Server Topic /v1/cm1/c2s Client ID {uuid} Qos 1 Retain 0Packet ID 1~65535 Application Message No. Offset Byte Type ContentsDescription Value Endian 1 0 4 unsigned Send Time Send Time Little int(second) 2 4 4 unsigned uuid Terminal Little int Unique Number 3 8 4unsigned Date Time Occurrence Little int Time (second) 4 12 1 unsignedDrive See Table 13 char Status 5 13 1 unsigned Event See Table 15 charCode 6 14 4 unsigned Cell ID Base Station Little int Information 7 18 2unsigned TAC Tracking Area Little short Code 8 20 1 unsigned GPS GPSStatus ‘A’ or char Status ‘V’ 9 21 4 unsigned Latitude WGS84 LatitudeLittle int 10 25 4 unsigned Longitude WGS8 4 Little int Longitude 11 291 unsigned DriveX Whether OBDII char is installed (see Table 14) 12 30 2unsigned Current Current Little short Battery Voltage Value 13 32 1unsigned Battery Current char Percent Remaining Voltage 14 33 2 unsignedLow Low-Voltage Little short Battery Setting Value 15 35 2 unsigned FuelDriving Fuel Little short Efficiency 16 37 4 unsigned Auth Server Littleint Number Authentication Number 17 41 1 unsigned Event See Table 16char Division Total Len 42

Table 12 below is a description of Time, Latitude/Longitude,Battery/Fuel, Battery Percent, and Auth Number fields among the fieldsof the data format (payload) of the MQTT PUBLISH (Table 11).

TABLE 12 Field Description Time Based on UNIX Time Stamp (January 1,1970, 0:0:0) : Second Latitude Convert Unit Value of Degree to Unit of0.01 second Longitude (sec) (Cutting Below Decimal Point) −Latitude:127.103427*3600*100=45757233 /Longitude:37.323876*3600*100=13436595 Battery / Value * 10 (12.1 * 10 =120) Fuel Battery Current Remaining Voltage (%) / 0 ~ 100 / When TherePercent is no Current Remaining Voltage : 0x00 Auth The details of theAuth Number Field are as shown Number in FIG. 52.

In addition, the content drive status of Table 11 described above may beconfigured as illustrated in Table 13 below. In Table 13 below, a normalmode may have the same meaning as the normal recording mode, which isone of the operation modes of the black box described above, and aparking mode may have the same meaning as the parking recording mode,which is one of the operation modes of the black box described above.

TABLE 13 Code Description 11 Start Driving/Normal Mode 12 StartDriving/Parking Mode 21 During Driving/Normal Mode 22 DuringDriving/Parking Mode 31 End Driving/Normal Mode 32 End Driving/ParkingMode 41 Start Dongle Update/Normal Mode 42 Start Dongle Update/ParkingMode 51 End Dongle Update/Normal Mode 52 End Dongle Update/Parking Mode

In addition, the content “DriveX” in Table 11 may be configured asillustrated in Table 14 below. Here, the OBD (On Board Diagnostics) mayrefer to a diagnostic standard for checking and controlling the overalloperating state of the vehicle.

TABLE 14 Code Description 0 OBDII is installed 1 OBDII is not installed

In addition, the content Event Code in Table 11 may be configured asillustrated in Table 15 below.

TABLE 15 Code Description 0 Normal 1 Impact 2 Black Box Power OFF 3 LowVoltage 4 Authentication Completion 5 Start ON 6 Start OFF 7 ParkingLocation Request Response 8 Image Request Response 9 Live Image RequestResponse 10 Start Dongle Update 11 End Dongle Update (Success) 12 EndDongle Update (Failure) 13 Impact During Normal Mode (SOS) 14 NormalMode Switching Reset 15 Image Count Initialization

In Table 15 described above, “Normal” may indicate that no eventoccurred, “Impact” may indicate an occurrence of an impact event, “BlackBox Power OFF” may indicate an occurrence of an event in which the powerof the black box is turned off, “Low Voltage” may indicate an occurrenceof an event in which a voltage value of the black box falls below apredetermined value or less, “Authentication Completion” may indicate anoccurrence of a user's authentication completion event for the userterminal device, “Start ON” may indicate an occurrence of an event inwhich the engine of the vehicle is turned on, “Start OFF” may indicatean occurrence of an event in which the engine of the vehicle is turnedoff, and “Parking Location Request Response” may indicate an occurrenceof a response event to a parking location request from the user terminaldevice.

In addition, “Image Request Response” may indicate an occurrence of aresponse event to an image request from the user terminal device. Here,the image request from the user terminal device may include an imagerequest from the parking location of the vehicle, and an image requestcorresponding to the impact event or the movement event of the vehicle.

In addition, “Live Image Request Response” may indicate an occurrence ofa response event to a live image request from the user terminal device,“Start Dongle Update” may indicate an occurrence of an update startevent of the dongle 200, “End Dongle Update (Success)” may indicate anoccurrence of a successful end event of the update of the dongle 200,“End Dongle Update (Failure)” may indicate an occurrence of a failureend event of the update of the dongle 200, “Impact During Normal Mode(SOS)” may indicate an occurrence of an emergency event in which animpact having a predetermined impact value or more is detected in thenormal mode, “Normal Mode Switching Reset” may indicate an occurrence ofan event in which the black box 100 switches from other modes to thenormal mode, and “Image Count Initialization” may indicate an occurrenceof an event in which the number of images that may be transmitted fromthe black box 100 is initialized. The update of the dongle 200 accordingto an exemplary embodiment of the present invention may be performed inan Over The Air (OTA) method, and may be performed when the distributionof the latest software for the dongle 200 is determined by themanufacturer of the dongle 200.

In addition, the content Event Division in Table 11 may be configured asillustrated in Table 16 below.

TABLE 16 Code Description 1 Including Image 2 Not Including Image 3Low-Voltage Power Off 4 Time-out Power Off 5 User Power Off 6 ServerRequest Power Off 7 Start OFF Power Off 8 Black Box Ultra Low Power Mode(SUSPEND) 9 While Transmitting Image (Upon Requesting On-Demand) 10Reboot (General) 11 Reboot (Start OFF)

That is, according to the present invention, the black box 100 and/orthe dongle 200 may generate event data including the time, the terminalunique number, the drive status, the event code, the location, and thedriving fuel efficiency, and transmit the generated event data to theserver.

If the MQTT server 301 receives the publish request (PUBLISH) forregistering the event from the dongle 200, the MQTT server 301 maytransmit the publish response (PUBLISH ACK) to the dongle 200.

On the other hand, when various commands for controlling the black box100 are input from the user terminal device 400, in contrast to theabove, the MQTT server 301 may transmit the publish request (PUBLISH)for registering the event to the dongle 200. In this case, as datatransmitted from the MQTT server 301 to the dongle 200, a data format ofthe MQTT PUBLISH ACK may be as illustrated in Table 17 below.

TABLE 17 Description Transmit Black Box Control Command from Server toCat.M1 Dongle (Authentication, Power OFF, Image Request) DirectionServer −> Client Topic /v1/cm1/s2c/{uuid} Qos 0 Retain 0 Packet ID1~65535 Application Message No. Offset Byte Type Contents DescriptionValue Endian 1 0 4 unsigned Send Time Send Time Little int (second) 2 44 unsigned Tid Transaction ID Little in 3 8 1 unsigned Command See Table20 char Code 4 9 2 unsigned External See Table 19 Little short Code 5 114 unsigned Auth Server Little int Number Authentication Number 6 15 16byte[ ] Reserved See Tables 21 to 25 Total Len 31

The description of the Time, Tid, and Reserved fields among the fieldsin Table 17 is as illustrated in Table 18 below.

TABLE 18 Field Description Time Based on UNIX Time Stamp (January 1,1970, 0:0:0) : Second Tid If not, Fill in with 0x00 and TransmitReserved If Command Code is not 114 or 115, 0x20 is Transmitted.

In addition, the content External Code in Table 17 may be configured asillustrated in Table 19 below.

TABLE 19 Description Operates as Follows according to Command CodeCommand Code Description 201 − Data Received in Black Box (Number) isTransmitted as It is

In addition, the content Command Code in Table 17 may be configured asillustrated in Table 20 below.

TABLE 20 Code Description 100 Power Off 102 Authentication Request(Transmit Authentication Number) 110 Vehicle Location Inquiry 111 ImageRequest 112 LIVE Check Request 113 Motion Image Request 114 ChangeDongle Settings 115 Set Traffic information 116 Dongle Initialization(RESET) Request / When Changing Service 117 Set Image Count 118 RemoteImage Playback Request 119 Transmit Downloaded Data 200 Cat.M1 FOTARequest 201 External Device Command Request 202 Safe Driving Data UpdateRequest

In addition, the content reservation field (Reserved) of Table 17 may beconfigured as illustrated in Tables 21 to 25 below according to a valueof the content command code.

TABLE 21 Description When Command Code is 114 No. Offset Byte TypeContents Description Endian 1 0 2 unsigned Image Time-out Image UploadLittle short Time 2 2 2 unsigned Image Write Image Packet Little shortTime-out Upload Time 3 4 2 unsigned Motion Image Motion Image Littleshort Time-out Upload Time 4 6 2 unsigned TCP Write TCP Write Littleshort Time-out Retransmission Time 5 8 2 unsigned TCP Retry TCP RetryLittle short Time-out Reconnection Time 6 10 1 unsigned TCP Write TCPWrite char Time-out Retransmission Count 7 11 1 unsigned TCP Retry TCPchar Count reconnection Count 8 12 1 unsigned Reset Time-out ResetInitial char Wait Time Total Len 13

TABLE 22 Description When Command Code is 115 No. Offset Byte TypeContents Description Endian 1 0 2 unsigned Traffic Traffic Little shortDay Pro Information Day Use (min) 2 2 1 unsigned Traffic Traffic charGather Information Gather Period (sec) 3 3 1 unsigned Traffic Trafficchar Report Information Transmission Period (sec) Total Len 4

TABLE 23 Description When Command Code is 117 No. Offset Byte TypeContents Description Endian 1 0 1 unsigned Motion Motion Image charImage Max Count 2 1 1 unsigned Park Parking Image char Image Max Count 32 1 unsigned Live Live Image char Image Max Count Total Len 3

TABLE 24 Description When Command Code is 118 No. Offset Byte TypeContents Description Endian 1 0 4 unsigned Event Time Impact Little intOccurrence Time (sec) 2 4 1 unsigned Play Type char Total Len 5 FieldDescription Event Time Based on UNIX Time Stamp (January 1, 1970,0:0:0): Second Play Type Impact Image Playback Camera Type The detailsof the Play Type Field are as shown in FIG. 53.

TABLE 25 Description When Command Code is 202 No. Offset Byte TypeContents Description Endian 1 0 10 unsigned Safe Guide Safe Driving charVer Data Version 2 4 4 unsigned Data Size Data File Little int Size(Byte) Total Len 14 Field Description Safe Guide Ver Ex > 19.08(T07)

That is, according to the present invention, the MQTT server 301 maygenerate event registration request data including various black boxcontrol commands such as the black box power off control command, thevehicle location inquiry request, the image request, the live checkrequest, and motion image request according to the request from the userterminal device 400, and transmit the generated event registrationrequest data to the dongle 200.

If the dongle 200 receives the publish request (PUBLISH) for registeringthe event from the MQTT server 301, the dongle 200 may transmit thepublish response (PUBLISH ACK) to the MQTT server 301.

Meanwhile, when the event is registered according to the above-describedprocess, the MQTT server 301 may register the event with the userterminal device 400, and the user terminal device 400 may display theregistered event through the display unit (S33).

FIG. 7 is a timing diagram illustrating an operation scenario of aconnected service system when uploading an image from a black boxaccording to an exemplary embodiment of the present invention. Referringto FIG. 7 , first, the black box 100 may transmit an image uploadrequest including image data (AT$BBIMG) to the dongle 200 (S41).

In addition, the dongle 200 may transmit and receive an imageregistration request and an image registration response, which is aresponse to the image registration request, to and from the TCP server302 (S42).

As an example, a data format of the image registration requesttransmitted from the dongle 200 to the TCP server 302 may be asillustrated in Table 26 below.

TABLE 26 Description Registration Request for Image Upload DirectionClient −> Server No. Offset Byte Type Contents Description Value Endian1 0 2 byte[ ] STX Packet Start 0x02 0x0E 2 2 1 unsigned Packet 0x53 charType 3 3 1 unsigned Total No. 4~No. 17 char Length Length 4 4 4 unsignedSend Time Send Time Little int (second) 5 8 4 unsigned Tid TransactionLittle int ID 6 12 4 unsigned uuid Terminal Little int Unique Number 716 4 unsigned Date Time Occurrence Little int Time (second) 8 20 1unsigned Drive See Table 13 char Status 9 21 1 unsigned Event See Table15 char Code 10 22 1 unsigned Event See Table 34 char Position 11 23 4unsigned Cell ID Base Station Little int Information 12 27 2 unsignedTAC Tracking Little short Area Code 13 29 1 unsigned GPS GPS Status ‘A’or char Status ‘V’ 14 30 4 unsigned Latitude WGS84 Little int Latitude15 34 4 unsigned Longitude WGS84 Little int Longitude 16 38 1 char ImgWhether ‘Y’ or Override There is New ‘N’ Image 17 39 4 unsigned ImgChunk Image Little int Len Division Criteria 18 43 2 byte[ ] ETX PacketEnd 0x03 0x0F Total Len 45

The description of the Tid and Img Chunk Len fields among the fields inTable 26 is as illustrated in Table 27 below.

TABLE 27 Field Description Tid If not, Fill in with 0x00 and TransmitImg Chunk Image Division Criteria (1,024 / 2,048 / 4,096) Len

In the exemplary embodiment of the present invention, when the dongle200 uploads the image to the TCP server 302, the image data to betransmitted is divided into chunks of units of shot time and transmittedfor efficient traffic transmission. In the exemplary embodiment of thepresent invention, the chunk, which is a unit for upload, may mean abundle of images corresponding to a certain size, a certain frame unit,and a certain number of frames. To this end, the TCP server 302 mayperform scheduling for time and bandwidth to upload the image to eachdongle 200 connected to the entire network for quality of service (QoS)management of the entire network. For example, the TCP server 302 mayperform scheduling in consideration of an urgency of the image to betransmitted by the dongle 200, a size of the image, the degree ofurgency according to the event type generated in the vehicle equippedwith the dongle 200, and an available bandwidth of the network. Suchscheduling may also be performed in the MQTT server 301, not the TCPserver 302.

In addition, a data format of the response to the image registrationrequest transmitted from the TCP server 302 to the dongle 200 may be asillustrated in Table 28 below.

TABLE 28 Description Registration Request Response for Image UploadDirection Server −> Client No. Offset Byte Type Contents DescriptionValue Endian 1 0 2 byte[ ] STX Packet Start 0x02 0x0E 2 2 1 unsignedPacket 0x54 char Type 3 3 1 unsigned Total No.4~No.7 char Length Length4 4 2 unsigned Code See Table 37 Little short 5 6 4 unsigned Image ImageLittle int uuid Classification ID 6 10 4 unsigned Img Chunk ImageDivision Little int Len Criteria 7 14 1 unsigned Img Chunk Image char NoCompletion Number 8 15 2 byte[ ] ETX Packet End 0x03 0x0F Total Len 17

That is, the image registration request according to the presentinvention may include event data such as a time corresponding to theimage registration request, a drive status, an event code, and locationinformation. Accordingly, the user receiving the connected service maybe able to check event-related information in the user terminal device400 as well as the event image. The TCP server 302 according to anexemplary embodiment of the present invention may perform scheduling forthe data to be uploaded by the dongle 200 according to field informationincluded in the image registration request message transmitted by thedongle 200.

Further, considering that the image is divided and transmitted accordingto the data transmission amount of the low-power wide-areacommunication, the data format according to the present invention mayinclude information such as the image division criteria and the imagecompletion number.

Meanwhile, the dongle 200 may transmit and receive an image uploadrequest and an image upload response, which is a response to the imageupload request, to and from the TCP server 302 (S43).

As an example, a data format of the image upload request transmittedfrom the dongle 200 to the TCP server 302 may be as illustrated in Table29 below.

TABLE 29 Description Image Upload Request Direction Client −> Server No.Offset Byte Type Contents Description Value Endian 1 0 2 byte [ ] STXPacket Start 0x02 0x0E 2 2 1 unsigned Packet 0x55 char Type 3 3 1unsigned Total No. 4~No. 7 char Length Length 4 4 4 unsigned Image ImageLittle int uuid Classification ID 5 8 4 unsigned Img No. 8 Length Littleint Length 6 12  1 unsigned Img Chunk Image Number char No 7 13  1unsigned Img Whether Image ‘Y’ or char Complete is Completed ‘N’ 8 14  nbinary Image Image 9 14+ 2 byte [ ] ETX Packet End 0x03 0x0F Total Len16 + n

In addition, a data format of the response to the image upload requesttransmitted from the TCP server 302 to the dongle 200 may be asillustrated in Table 30 below.

TABLE 30 Description Image Upload Request Response Direction Server −>Client No. Offset Byte Type Contents Description Value Endian 1 0 2 byte[ ] STX Packet Start 0x02 0x0E 2 2 1 unsigned Packet 0x56 char Type 3 31 unsigned Total No. 4~No. 5 char Length Length 4 4 2 unsigned Code SeeTable 37 Little short 5 6 1 unsigned Image Image char Count RemainingCount 6 7 2 byte [ ] ETX Packet End 0x03 0x0F Total Len 8 FieldDescription Image Count Image Remaining Count − 1 0: During ImageTransmission, where Dongle Ignores Corresponding Value 1: No ImageRemaining Count 11: Image Remaining Count of 10

Here, the image upload request may include an upload image, and theimage upload process may be repeated until the image upload iscompleted.

Meanwhile, when the image registration is completed, the TCP server 302may notify the user terminal device 400 of the image registration, andthe user terminal device 400 may display the received image through thedisplay unit (S44).

A process in which S44 is performed in the user terminal device 400 willbe described as follows as an example. When the TCP server 302 notifiesthe user terminal device 400 in the form of a push message that theimage upload from the dongle 200 is completed, the user terminal device400 displays the image upload completion in a pop-up form to the userthrough the display unit. If the user clicks the displayed pop-upmessage, the user terminal device 400 downloads the image uploaded tothe TCP server 302 and displays the downloaded image to the user.

FIG. 8 is a timing diagram illustrating an operation scenario of aconnected service system when an image is requested by a user terminaldevice according to an exemplary embodiment of the present invention.Referring to FIG. 8 , first, the user terminal device 400 may transmitan image request to the MQTT server 301 (S51). Here, an example of theimage request from the user terminal device 400 may include a live imagerequest requesting an image captured in real time in the black box 100and a parking location image request requesting an image of a parkinglocation of the vehicle.

Then, the MQTT server 301 may transmit and receive the publish request(PUBLISH) and the publish response (PUBLISH ACK) to and from the dongle200 (S52). Here, the data format for the publish request (PUBLISH) maybe as illustrated in Table 11, and the data format for the publishresponse (PUBLISH ACK) may be as illustrated in Table 17.

Then, the dongle 200 may transmit an image request ($BBIMGREQ) to theblack box 100 (S53), and the black box 100 may transmit a responseincluding an image (AT$BBIMG) to the dongle 200 (S54).

In addition, the dongle 200 may transmit and receive an imageregistration request and an image registration response, which is aresponse to the image registration request, to and from the TCP server302 (S55). Here, the data format for the image registration request maybe as illustrated in Table 26. In addition, the data format of theresponse to the image registration request may be as illustrated inTable 28.

Thereafter, the dongle 200 may transmit and receive an image uploadrequest and an image upload response, which is a response to the imageupload request, to and from the TCP server 302 (S56). Here, the dataformat for the image upload request may be as illustrated in Table 29.In addition, the data format of the response to the image upload requestmay be as illustrated in Table 30.

Meanwhile, when the upload of the image is completed, the TCP server 302may register the image in the user terminal device 400, and the userterminal device 400 may display the received image through the displayunit (S57).

FIG. 9 is a timing diagram illustrating an operation scenario of aconnected service system when a power off request is made in a black boxaccording to an exemplary embodiment of the present invention. Referringto FIG. 9 , first, the black box 100 may transmit a power off request(AT$CMNPWDN) of the black box 100 to the dongle 200 (S61).

Then, the dongle 200 may transmit and receive the publish request(PUBLISH) and the publish response (PUBLISH ACK) to and from the MQTTserver 301 (S62). Here, the data format for the publish request(PUBLISH) may be as illustrated in Table 11, and the data format for thepublish response (PUBLISH ACK) may be as illustrated in Table 17.

Then, the MQTT server 301 may register the power off (POWER OFF) of theblack box 100 in the user terminal device 400, and the user terminaldevice 400 may display that the power of the black box is turned offthrough the display unit (S63).

Then, the dongle 200 may disconnect a communication connection with theMQTT server 301 (S64), transmit a Detach Request to the base station500, and perform a Detach procedure with the base station 500 (S65).

Here, a disconnect message transmitted from the dongle 200 to the MQTTserver 301 may be configured as a protocol as illustrated in Table 31below.

TABLE 31 Type bit 7 6 5 4 3 2 1 0 Fixed byte Message Type (14) Reservedheader 1 byte Remaining length (0) 2.N

Meanwhile, if the communication connection of the dongle 200 isdisconnected according to the process described above, the dongle 200may transmit a power supply blocking request ($NOSVC) to the black box100 (S66), and the black box 100 may block power supply to the dongle200 (S67). In addition, in S67, the black box 100 may also notify thedongle 200 that operation power supply is blocked.

FIG. 10 is a timing diagram illustrating an operation scenario of aconnected service system when a black box is powered off according to arequest of a user terminal device according to an exemplary embodimentof the present invention. Referring to FIG. 10 , first, the userterminal device 400 may transmit a power off request of the black box100 to the MQTT server 301 (S71). Then, the MQTT server 301 may transmitand receive the publish request (PUBLISH) and the publish response(PUBLISH ACK) to and from the communication apparatus 200 for a vehicle(S72). Here, the data format for the publish request (PUBLISH) may be asillustrated in Table 11, and the data format for the publish response(PUBLISH ACK) may be as illustrated in Table 17.

Then, the dongle 200 may transmit a black box power-off request ($BBOFF)to the black box 100 (S73), and the black box 100 may transmit a poweroff response (AT$CMNPWDN) indicating that the black box 100 is poweredoff to the dongle 200 (S74).

Then, the MQTT server 301 and the dongle 200 may transmit and receivethe publish request (PUBLISH) and the publish response (PUBLISH ACK)(S75). Here, the data format for the publish request (PUBLISH) may be asillustrated in Table 11, and the data format for the publish response(PUBLISH ACK) may be as illustrated in Table 17.

Then, the MQTT server 301 may register the power off of the black box100 in the user terminal device 400, and the user terminal device 400may display that the power of the black box is turned off through thedisplay unit (S76). At this time, in S76, the MQTT server 301 may notifythe power off of the black box 100 to the user terminal device 400through a push message, and the user terminal device 400 may display thepower off of the black box 100 to the user through a pop-up message.

Then, the dongle 200 may disconnect the communication connection withthe MQTT server 301 (S77), and transmit a Detach Request to the basestation 500 (S78).

Then, the dongle 200 may transmit a power supply blocking request($NOSVC) to the black box 100 (S79), and the black box 100 may blockpower supply to the dongle 200 (S80).

On the other hand, according to FIGS. 5 to 10 described above, byclassifying the server 300 into the MQTT server 301 and the TCP server302 from a protocol perspective, it has been described as an examplethat the event registration, the power off registration, and the likeare performed through the MQTT server 301 and the image registration andupload are performed through the TCP server 302, but the presentinvention is not limited thereto, and according to another exemplaryembodiment of the present invention, the processes described above maybe performed without classifying the server.

FIG. 11 is a timing diagram illustrating a motion image upload processaccording to an exemplary embodiment of the present invention. Here, themotion image is generated by combining at least two images, not oneimage, to express the movement of an object in the image, and the imageand the motion image may be different from each other.

Referring to FIG. 11 , first, the black box 100 may transmit a motionimage upload request (AT$BBMIMG) corresponding to a front capturingimage to the dongle 200 (S101), and the dongle 200 may transmit a motionimage registration request to the server 300 (S102).

Here, a data format of the motion image registration request transmittedfrom the dongle 200 to the server 300 may be as illustrated in Table 32below.

TABLE 32 Description Registration Request Data for Motion Image UploadDirection Client −> Server No. Offset Byte Type Contents DescriptionValue Endian 1 0 2 byte [ ] STX Packet Start 0x02 0x0E 2 2 1 unsignedPacket 0x57 char Type 3 3 1 unsigned Total No. 4~No. 19 char LengthLength 4 4 4 unsigned Send Time Send Time Little int (second) 5 8 4unsigned Tid Transaction Little int ID 6 12 4 unsigned uuid TerminalLittle int Unique Number 7 16 4 unsigned Date Time Occurrence Little intTime (second) 8 20 1 unsigned Drive See Table 13 char Status 9 21 1unsigned Event See Table 15 char Code 10 22 1 unsigned Event See Table34 char Position 11 23 4 unsigned Cell ID Base Station Little intInformation 12 27 2 unsigned TAC Tracking Little short Area Code 13 29 1unsigned GPS GPS Status ‘A’ or char Status ‘V’ 14 30 4 unsigned LatitudeWGS84 Little int Latitude 15 34 4 unsigned Longitude WGS84 Little intLongitude 16 38 1 char All Whether ‘Y’ or Override Entire File ‘N’ isCompleted 17 39 4 unsigned Img Chunk Image Little int Len DivisionCriteria 18 43 1 unsigned Img Count Total Number char of Images 19 44 1unsigned Cam Number of char Channel Camera Channels 20 45 2 byte [ ] ETXPacket End 0x03 0x0F Total Len 47

The description of the All Override, Img Chunk Len, and Img Count fieldsamong the fields in Table 32 is as illustrated in Table 33 below.

TABLE 33 Field Description All Override Whether There is New EntireMotion Image Img Chunk Len Image Division Criteria (1,024 / 2,048 /4,096 ⊚) Img Count Total Number of Motion Image Files

That is, since the motion image according to the present invention isgenerated by combining a plurality of images, the registration requestfor a motion image upload may further include “total number of images”information compared to the registration request for an image uploadillustrated in Table 26.

In addition, the content Event Position in Table 32 may be configured asillustrated in Table 34 below.

TABLE 34 Code Description 10 Front Image 20 Rear Image 30 Left Image 40Right Image

Then, the server 300 may transmit a response to the motion imageregistration request to the dongle 200 (S103).

Here, a data format of the response to the image registration requesttransmitted from the server 300 to the dongle 200 may be as illustratedin Table 35 below.

TABLE 35 Description Registration Request Response Message for MotionImage Upload Direction Server −> Client No. Offset Byte Type ContentsDescription Value Endian 1 0 2 byte [ ] STX Packet Start 0x02 0x0E 2 2 1unsigned Packet 0x58 char Type 3 3 1 unsigned Total No. 4~No. 8 charLength Length 4 4 2 unsigned Code See Table 37 Little short 5 6 4unsigned Image Image Little int uuid Classification ID 6 10 4 unsignedImg Chunk Image Division Little int Len Criteria 7 14 1 unsigned ImgFile Image File char No Completion 8 15 1 unsigned Img Chunk Image charNo Completion Number 9 16 2 byte [ ] ETX Packet End 0x03 0x0F Total Len18

The description of the Img Chunk Len, Img File No, and Img Chunk Nofields among the fields in Table 35 is as illustrated in Table 36 below.

TABLE 36 Field Description Img Chunk Len Image Division Criteria (1,024/ 2,048 / 4,096 ⊚) Img File No Image File Completion Number / 1 Copy isReceived : 1 Img Chunk Image Division Completion Number / Based on ImgChunk No No Transmitted by Dongle

That is, the registration request response for motion image uploadaccording to the present invention may further include “image filecompletion” information compared to the registration request responsefor image upload illustrated in Table 28.

In addition, the content Code in Table 35 may be configured asillustrated in Table 37 below.

TABLE 37 Code Description 0 SUCCESS (Cat.M1 Pro Version) 100 NB-IoT LiteVersion 101 NB-IoT Standard Version 200 Dongle Not Supported by BlackBox (Service Not Supported) 300 Dongle Version Not Supported by BlackBox (Required Dongle Upgrade) 2400 BAD REQUEST 2401 Please Log in Again2403 ACCESSDENIED 2500 SERVER ERROR 2501 Not SubScribe 2502 Period ofUse Remains Less Than 12 Months 2510 Fail to Regist 2511 Invalid UUID2512 NOT Image Init Request 2513 Already Saved Imaged 2900 UNKNOWN ERROR2901 NOT FOUND USERINFO 2902 NOT FOUND NBIOT_INFO 2903 ALREADY EXISTSEMAIL 2904 Invalid Exception

Thereafter, the dongle 200 may transmit a motion image upload request tothe server 300 (S104). Here, a data format of the motion image uploadrequest transmitted from the dongle 200 to the server 300 may be asillustrated in Table 38 below.

TABLE 38 Description Motion Image Upload Request Direction Client −>Server No. Offset Byte Type Contents Description Value Endian 1 0 2 byte[ ] STX Packet Start 0x02 0x0E 2 2 1 unsigned Packet 0x59 char Type 3 31 unsigned Total No. 4~No. 9 char Length Length 4 4 4 unsigned ImageImage Little int uuid Classification ID 5 8 4 unsigned Img No. 11 LengthLittle int Length 6 12  1 unsigned Img File Image File char No Number 713  1 unsigned All Whether All are ‘Y’ or char Complete Completed ‘N’ 814  1 unsigned Img Image Number char Chunk No 9 15  1 unsigned ImgWhether Image ‘Y’ or char Complete is Completed ‘N’ 10 16  n binaryImage Image 11 16+ 2 byte [ ] ETX Packet End 0x03 0x0F Total Len 18 + n

That is, since the motion image according to the present invention isgenerated by combining the plurality of images, the motion image uploadrequest may further include information on an image file number andwhether all are completed compared to the registration request for imageupload illustrated in Table 29.

Then, the server 300 may transmit a response to the motion image uploadrequest to the dongle 200 (S105). Here, a data format of the response tothe image upload request transmitted from the server 300 to the dongle200 may be as illustrated in Table 39 below.

TABLE 39 Description Motion Image Upload Request Response DirectionServer −> Client No. Offset Byte Type Contents Description Value Endian1 0 2 byte [ ] STX Packet Start 0x02 0x0E 2 2 1 unsigned Packet 0x60char Type 3 3 1 unsigned Total No. 4~No. 5 char Length Length 4 4 2unsigned Code See Table 37 Little short 5 6 1 unsigned Image Image charCount Remaining Count 6 7 2 byte [ ] ETX Packet End 0x03 0x0F Total Len9

When the number of times the dongle 200 may upload the image to theserver 300 is limited, the Image Count field among the fields in Table39 may be used for counting the limited number of times. For example, ifthe service subscribed by the user may upload the image only 10 timesper day (total number of times of uploads per day=10), the server 300may count the number of times of images uploaded by the dongle 200, andmay transmit the uploadable number of times after subtracting thecounted number of times from the total number of times of uploads perday to the dongle 200 through the Image Count field. Through this, theblack box 100 may display to the user the number of times of uploads ofthe current image among the total number of times of uploads per day, orthe uploadable number of times.

The description of the Image Count field among the fields in Table 39 isas illustrated in Table 40 below.

TABLE 40 Field Description Image Image Remaining Count − 1 Count 0 :During Image Transmission, where Dongle Ignores Corresponding Value 1 :No Image Remaining Count 11 : Image Remaining Count of 10

In this case, S104 to S105 may be repeatedly performed as many times asthe number of pictures to be transmitted to the server 300. A pluralityof pictures transmitted to the server 300 may be used to generate amotion image for the front of the vehicle.

In addition, if the number of images required to generate a motion imagefor the front of the vehicle has been sufficiently uploaded, the server300 may notify the dongle 200 that the upload of the entire frontpicture has been completed (S106), and the dongle 200 may transmit amotion image upload completion response ($BBMIMG:0) for the front to theblack box 100 (S107).

In addition, the black box 100 may transmit a motion image uploadrequest (AT$BBMIMG) for a rear capturing image to the dongle 200 (S108),and the dongle 200 may transmit a motion image registration request forthe rear capturing image to the server 300 (S109). Then, the server 300may transmit a response to the motion image registration request to thedongle 200 (S110). Here, a data format of the motion image uploadrequest in S109 may be as illustrated in Table 32, and the response tothe motion image registration request in S110 may be as illustrated inTable 35.

Thereafter, the dongle 200 may transmit a motion image upload request tothe server 300 (S111). Here, a data format of the motion image uploadrequest transmitted from the dongle 200 to the server 300 may be asillustrated in Table 38.

Then, the server 300 may transmit a response to the motion image uploadrequest to the dongle 200 (S112). Here, a data format of the response tothe motion image upload request transmitted from the server 300 to thedongle 200 may be as illustrated in Table 39.

In this case, S111 and S112 may be repeatedly performed as many times asthe number of pictures to be transmitted to the server 300. A pluralityof pictures transmitted to the server 300 may be used to generate amotion image for the rear of the vehicle.

In addition, the server 300 may notify the dongle 200 that the upload ofthe entire rear picture has been completed (S113), and the dongle 200may transmit a motion image upload completion response ($BBMIMG:0) forthe rear to the black box 100 (S114).

In FIG. 11 , as images for motion image registration, only the imagesfor the front and rear of the vehicle are described as an example, butthe present invention is not limited thereto. For example, the image formotion image registration according to the present invention may be animage captured in any direction such as in front, rear, left, or rightof the vehicle, and may also be an image captured according to a controlcommand received from the user terminal device 400.

Meanwhile, although not illustrated in the above-described drawings, theconnected service system 1000 according to an exemplary embodiment ofthe present invention may also transmit data to another external device.In this case, a data format of another external device interworkingrequest transmitted from the dongle 200 to the server 300 forinterworking with another external device may be as illustrated in Table41 below.

TABLE 41 Description Black Box External Device Interlocking DataTransmission Direction Client −> Server No. Offset Byte Type ContentsDescription Value Endian 1 0 2 byte [ ] STX Packet Start 0x02 0x0E 2 2 1unsigned Packet 0x61 char Type 3 3 2 unsigned Total No. 4~No. 7 Littleshort Length Length 4 5 4 Unsigned uuid Terminal Little int UniqueNumber 5 9 1 unsigned Data No Data Number char 6 10  1 unsigned AllWhether All ‘Y’ or char Complete are Completed ‘N’ 7 11  n binary DataExternal Device Data 8 11+ 2 byte [ ] ETX Packet End 0x03 0x0F Total Len13 + n

In addition, a data format of a response to another external deviceinterworking request transmitted from the server 300 to the dongle 200may be as illustrated in Table 42 below.

TABLE 42 Description Black Box External Device Interlocking DataTransmission Response Direction Server −> Client No. Offset Byte TypeContents Description Value Endian 1 0 2 byte [ ] STX Packet Start 0x020x0E 2 2 1 unsigned Packet 0x62 char Type 3 3 2 unsigned Total No. 4~No.5 Little short Length Length 4 5 2 unsigned Code See Table 37 Littleshort 5 7 n binary Data Downloaded Data 6  7+ 2 byte [ ] ETX Packet End0x03 0x0F Total Len  9+ Field Description Data Download data(Binary)/Max 1 KB (1,024 Byte)

In addition, although not illustrated in the above-described drawings,the connected service system 1000 according to an exemplary embodimentof the present invention may also transmit ADAS data.

In addition, a safe driving data version transmission format transmittedfrom the dongle 200 to the server 300 may be as illustrated in Table 43below.

TABLE 43 Description Black Box Safe Driving Data Version TransmissionDirection Client −> server No. Offset Byte Type Contents DescriptionValue Endian 1 0 2 byte [ ] STX Packet Start 0x02 0x0E 2 2 1 unsignedPacket 0x63 char Type 3 3 1 unsigned Total No. 4~No. 5 char LengthLength 4 4 4 Unsigned uuid Terminal Little int Unique Number 5 8 10string Safe Safe Driving Guide Ver Version 6 18 2 byte [ ] ETX PacketEnd 0x03 0x0F Total Len 20

Among the fields in Table 43, the Safe Guide Ver field is a fieldincluding a safe driving data version. The server 300 may provide safedriving data of the black box 100 in an OTA manner by comparing the safedriving data version of the black box 100 transmitted through the dongle200 and the latest version of the safe driving data version, and theblack box 100 may update the safe driving data received from the server300 with the latest version data.

The safe driving data may be data for a safety guide required for roaddriving and route driving guidance, and may include, for example, newroad generation, traffic light generation, specific area setting such asa school zone, traffic regulation revision, new speed limit sectioninformation, and the like.

Among the fields in Table 43, Safe Guide Ver may be utilized asillustrated in Table 44 below.

TABLE 44 Field Description Safe Guide Ex> 19.08 (T07) Ver

In Table 44, the Safe Guide Ver field indicates that the safe drivingdata currently stored in the black box 100 is data that expires after2019.08. That is, the Safe Guide Ver field may be set to notify when thesafe driving data stored in the black box 100 is updated.

In addition, a data format of a safe driving data version transmissionresponse transmitted from the server 300 to the dongle 200 may be asillustrated in Table 45 below.

TABLE 45 Description Black Box Safe Driving Data Version TransmissionResponse Direction Server −> Client No. Offset Byte Type ContentsDescription Value Endian 1 0 2 byte [ ] STX Packet Start 0x02 0x0E 2 2 1unsigned Packet 0x64 char Type 3 3 1 unsigned Total No. 4 Length charLength 4 4 2 unsigned Code Server Little short Response Code 5 6 2 byte[ ] ETX Packet End 0x03 0x0F Total Len 8

In addition, although not illustrated in the above-described drawings,the connected service system 1000 according to an exemplary embodimentof the present invention may transmit and receive traffic information.In this case, a header of a data format for traffic information requesttransmitted from the dongle 200 to the server 300 may be configured asillustrated in Table 46 below.

TABLE 46 Description Cat.M1 Dongle Traffic Information Header DirectionClient −> Server No. Offset Byte Type Contents Description Value Endian1 0 1 unsigned Log 0x02/ Little char Version 0x12 2 1 1 unsignedFunction 0x00 Little char Flag 3 2 1 unsigned Body 1~255 Little charCount 4 3 1 unsigned Reserved 0x00 Little int 5 4 4 unsigned DeviceLittle int Number 6 8 4 unsigned Time Little int Stamp 7 12 4 unsignedLatitude WGS84 Little int 8 16 4 unsigned Longitude WGS84 Little intTotal Len 20

The description of the Log Version, Function Flag, Device Number, TimeStamp, Latitude, and Longitude fields among the fields in Table 46 is asillustrated in Table 47 below.

TABLE 47 Field Description Log 0x02 : Existing Interworking StandardVersion 0x12 : ADAS Additional Interworking Standard Function Thedetails of the Function Flag Field are as shown Flag in FIG. 54. DeviceTerminal Phone Number (CTN) Number Ex> 012-1234-5678 −> 12345678 isconverted to number and unsigned Time Transmit as integer Stamp Based onUNIX Time Stamp (January 1, 1970, 0:0:0) : Second Latitude Convert UnitValue of Degree to Unit of 0.01 second Longitude (sec) (Cutting BelowDecimal Point) Latitude 127.103427 * 3600 * 100 = 45757233 Longitude37.323876 * 3600 * 100 = 13436595

In addition, an ADAS data format body transmitted from the dongle 200 tothe server 300 may be as illustrated in Table 48 below.

TABLE 48 Description Cat.M1 Dongle ADAS Data Format Body DirectionClient −> Server No. Offset Byte Type Contents Description Value Endian1 0 2 signed Latitude Little short Diff. 2 2 2 signed Longitude Littleshort Diff 3 4 1 unsigned Time char Stamp Diff 4 5 1 unsigned HDOP 0~250char 5 6 1 unsigned Course 0~179 char 6 7 1 unsigned Speed 0~255 Km/hchar 7 8 1 unsigned ADAS Log char Event Version: 0x12 Total Len 9

The description of the Latitude/Longitude, Time Stamp Diff, HDOP,Course, Speed, and ADAS Event fields among the fields in Table 48 is asillustrated in Table 49 below.

TABLE 49 Field Description Latitude Value Changed Based onLatitude/Longitude of Header Longitude Header Latitude/Longitude =45757997/13435657 Current Latitude/Longitude = 45757986/13435605 BodyLatitude/Longitude Calculation = 45757986 − 45757997 = −11 / 13435605 −13435657 = 52 Time Stamp Value Changed Based on Time Stamp Value ofHeader Diff HDOP Actual HDOP (0.0 to 50.0) Value X 5 (Multiplication 5)Course Actual Course (0 to 359) value / 2 (Division 2) Speed Unit inKm/h, but Fixed to 255 in Case of 255 Km/h or More ADAS Event Thedetails of the ADAS Event Field are as shown in FIG. 55.

In addition, referring to Tables 48 and 49, according to an exemplaryembodiment of the present invention, the ADAS data message transmittedfrom the dongle 200 to the server 300 includes difference informationbetween the previously generated location information and the time stampand the currently generated location information and the time stamp, notfull information of location information and time stamp information inheader information of the ADAS data message in order to minimize a sizeof the transmitted message. That is, if there is location informationand time stamp information in which the ADAS data message to betransmitted from the dongle 200 to the server 300 is previouslygenerated, and a new ADAS data message is generated by a specific event,the dongle 200 may reduce data usage compared to the existing data usageby transmitting only a difference (Latitude diff/Longitude diff) betweenthe previously generated location information and the newly generatedlocation information and difference (Time Stamp Diff) informationbetween the previously generated time stamp and the newly generated timestamp to the server 300.

In addition, the body of the ADAS data format transmitted from thedongle 200 to the server 300 may include ADAS event information. Here,only the lane departure warning system (LDWS) and the front vehiclecollision warning system (FCWS, uFCWS) are described as examples of theADAS event information, but the ADAS event information may furtherinclude a front vehicle start alarm (FVSA), a traffic light change alarm(TLCA), a pedestrian detection and collision alarm (PDCA), and the like.

According to the protocol of the present invention, the data usage maybe reduced to be suitable for the low-power wide-area communication byoptimizing data compared to a conventional method. That is, according tothe present invention, by changing the existing Jason method to theBinary method, and transmitting data that used an average of 200 bytesfor all events in the existing header as TCP-based raw data to zero thedata, the data usage may be reduced to be suitable for the low-powerwide-area communication. Table 50 below is a table for explaining animprovement effect according to the protocol according to the presentinvention.

TABLE 50 NB-IOT Method Existing According NB-IOT to PresentClassification Method Invention Communication Usage 482 KB 226 KB WhenSwitching from (Saving 53%) Normal Mode to Parking Mode (Standard: 125times/month) Impact Event 225 KB 39 KB Communication Usage (Saving 83%)(Standard: 625 impacts/month) Impact Event 6.91 MB 3.16 MB CommunicationUsage (Saving 54%) (Standard: 625 impacts/month) Other Communication 88KB 16 KB Usages (Saving 82 KB) (Power off 60 times/month, BatteryVoltage Value 150 times/month) TOTAL 7.69 MB 3.43 MB (Saving 55%)

Meanwhile, the connected system 1000 according to an exemplaryembodiment of the present invention may provide the connected serviceaccording to the present invention based on the above-describedprotocol. The connected service may be performed by, when a connectedservice application is executed in the user terminal device 400, theuser terminal device 400 accessing the server 300 to acquire variousdata (e.g., data acquired by the image capturing apparatus 100 for avehicle) stored in the server 300 and generating various user interfacesbased on the acquired data to display the various user interfaces on ascreen.

Hereinafter, an implementation example of the connected serviceaccording to an exemplary embodiment of the present invention will bedescribed in more detail with reference to the subsequent drawings.

FIGS. 12A to 12C are diagrams illustrating a main user interfaceaccording to an exemplary embodiment of the present invention. Here, themain user interface is an interface displayed when the connected serviceapplication according to the present invention is first executed, andthe interface may be configured by the user terminal device 400receiving, from the server 300, the data transmitted from the black box100 and the dongle 200 to the server 300 according to the processesdescribed above with reference to FIGS. 5 to 11 . As an example, theuser terminal device 400 displays an executable object for providinginformation about user content to a user on the display unit in the formof user experience (UX), and receives and provides data corresponding toan input from the server 300 when a selection for the executable objectdisplayed on the display unit is input by the user. For example, if theapplication for providing a connected service according to an exemplaryembodiment of the present invention is installed on the user terminaldevice 400, the user terminal device 400 executes the application by theuser inputting an execution command (click, voice control, and the like)for the application. In addition, the user terminal device 400 requestsvarious data selected by the user from the UX screen provided to theuser to the server 300, and receives and provides the requested data tothe user. Through such a method, the user terminal device 400 maydisplay a notification about various events such as information of theblack box 100 which is remotely separated, a vehicle impactnotification, a vehicle movement detection notification, and imagescaptured by the black box 100.

Specifically, referring to FIG. 12A, a main user interface 1101 maydisplay connection status information of the black box 100 connected tothe server 300, a vehicle image, and an event notification icon for thevehicle. At this time, a screen illustrated in FIG. 12A may be displayedafter authentication is completed through a registration procedure forthe black box 100 and the user of the user terminal device 400.

Referring to FIGS. 12A to 12C, as an example, in the UX screen of theapplication provided to the user, an operation mode of the black box 100may be displayed to be visually distinguished as a border color of avehicle image object. As an example, when the operation mode of theblack box 100 is in the parking mode and in the normal mode, the bordercolor of the vehicle image object may be changed and displayeddifferently. As another example, the user may also visually distinguisheach operation mode by using representative text indicating theoperation mode of the black box 100. For example, in the case of theparking mode, an alphabet “P” may be displayed on the vehicle image, andin the case of the normal mode, an alphabet “N” may be displayed on thevehicle image.

As another example, the border color of the vehicle image object mayalso display a positive/negative state of the vehicle. As an example,the border color of the vehicle image object may be displayed in a redcolor in various dangerous situations, such as when there is an impacton the vehicle, when a movement of the vehicle is detected, or when adanger is detected during the ADAS function. However, the border colorof the vehicle image object may be displayed in a green color when thevehicle is parked or in a safe situation.

As another example, when an impact event occurs while parking or drivingthe vehicle, the application may display an impact notification icon1103 on the vehicle image as a visual object informing the occurrence ofthe impact event on the vehicle, as illustrated in FIG. 12B. In thiscase, the visual object may be modified and displayed according to themagnitude of an impact value received from the server 300. For example,a size of an icon may be changed, or different icons or a color of theicon may be changed and displayed. As another example, when the impactevent occurs while parking or driving the vehicle, the application maydisplay the occurrence of the event in the form of generating vibrationon the vehicle image. For example, the magnitude of the vibration of thevehicle image may also be adjusted and displayed according to the degreeor frequency of occurrence of the event. At this time, as a method ofdisplaying the vibration of a vehicle image, the vibration may bedisplayed by vibrating the vehicle image in the left and right or up anddown directions to move the vehicle image, and may also be displayed bya vibration animation method.

As another example, when a movement of the vehicle is detected whileparking the vehicle, a visual object (e.g., an arrow icon 1104)informing a movement event of the vehicle may be displayed on thevehicle image as illustrated in FIG. 12C. In this case, a movementdirection of the vehicle may be displayed by a corresponding arrow basedon the direction and/or size of the impact value received from theserver 300.

Meanwhile, a region 1105 of the main user interface 1101 may displayinformation (product name, and the like) of the black box 100 connectedto a smartphone, and connection status information of the black box 100as a visual object.

In addition, a region 1106 of the main user interface 1101 is a regionfor displaying vehicle status information, and may display the currentvehicle's mode (parking mode/driving mode) information, the vehicle'sbattery status information (e.g., a vehicle's battery current value anda drivable distance), and secondary battery information (e.g., display apercentage of remaining battery) when a secondary battery is mounted, asvisual objects.

Specifically, a region 1106-1 may display a current vehicle's mode, forexample, a normal mode and a parking mode.

In addition, a region 1106-2 may display the vehicle's battery statusinformation (e.g., the vehicle's battery current value).

In addition, a region 1106-3 may display current status information ofthe black box and/or the vehicle. For example, the region 1106 maydisplay various information such as vehicle safety, vehicle impactoccurrence, vehicle movement detection, a need to check the connectionstatus of the black box communication, a black box ultra-low power mode,black box communication module update, and the like, as visual objects.

In addition, a region 1106-4 may display driving fuel efficiencyinformation and a corresponding icon. As an example, when an averagefuel efficiency of the vehicle is higher than a preset value, theaverage fuel efficiency of the vehicle and an “ECO” icon may bedisplayed. If the user selects the “ECO” icon, the user terminal device400 may display a detailed fuel efficiency statistics screen.

In addition, a region 1106-5 may display parking elapsed timeinformation and a corresponding icon. Here, the parking elapsed time maymean a time difference from a time when the vehicle is parked to acurrent time. If the user selects the parking elapsed time icon, theuser terminal device 400 may display a user interface displaying thelast parking location of the vehicle. Here, the user interfacedisplaying the last parking location may be as illustrated in FIGS. 15to 17 .

If there is no information on the last parking location of the vehicle,the user terminal device 400 may display location information set as adefault in the region 1106.

Meanwhile, a region 1107 is a live button, and if the region 1107 isselected, the user terminal device 400 may request a real-time capturingimage to the black box 100 through the server 300, and may display auser interface displaying an image captured in real time in the blackbox 100 received through the server 300 according to the request. Here,the user interface displaying the real-time image may be as illustratedin FIGS. 23A to 23C.

In addition, a region 1108 is a black box off button, and if the region1108 is selected, the user terminal device 400 may generate a controlsignal for powering off the black box 100 and transmit the controlsignal to the server 300.

In addition, a region 1109 is a button of turning on/off an engine ofthe vehicle, and the ON/OFF state of the vehicle's start may bedisplayed by whether an LED of the region 1109 is turned on/off. If theregion 1109 is selected, the user terminal device 400 may generate acontrol signal for turning on/off the engine of the vehicle and transmitthe control signal to the server 300.

In addition, a region 1110 is a weather information display region, andmay display phrases related to an address, weather, and a vehicle, atemperature, and a weather icon based on the location of the userterminal device 400. Here, the phrase related to the vehicle may mean auseful phrase related to the vehicle based on a current weather, such as“Today is a good day to wash a car.”

In addition, a region 1111 is a display region of my drivinginformation, and may display a driving accumulation record for apredetermined period (e.g., the last 7 days). If there is a day when thedriving has not been performed for a predetermined period, the displayregion 1111 of my driving information may display the remaining drivinginformation except for information on the corresponding day. The mydriving information displayed in the region 1111 is a visual display ofthe driving accumulation record of the vehicle, and may be referred toas driving history information, and may be displayed as a visual object(e.g., a size of a circle) capable of distinguishing between many andfew accumulated driving distances for each date.

Here, the driving information displayed through the region 1111 mayinclude at least one of event information generated while driving thevehicle, such as sudden deceleration, sudden acceleration, over-speed,forward collision warning, and lane departure warning. In addition, thedriving information displayed for each date in the region 1111 maydisplay a visual object corresponding to the number of times of eventsoccurring on the corresponding date. For example, as the number of timesof events that occurred is larger, a larger size circle may bedisplayed, and as the number of times of events that occurred issmaller, a relatively smaller size circle may be displayed.

In addition, the driving information may be displayed in the order ofthe sudden deceleration, the sudden acceleration, the over-speed, theforward collision warning, and the lane departure warning, and eachcircle of the region 1111 may be an icon representing the suddendeceleration/sudden acceleration/over-speed/front collision warning/lanedeparture warning from left to right. Here, different colors may bemapped to the region 1111 for each driving information.

In addition, a date expression method in the region 1111 may be providedin a time order, such as today/yesterday/2 days ago/3 days ago/4 daysago/5 days ago/6 days from the left.

If there is no driving information, the region 1111 may be provided witha phrase such as “There is no driving record. Start driving.”

Meanwhile, when the driving information of a specific date is selected,the user terminal device 400 may display a user interface that displaysdriving information of the selected date in detail.

On the other hand, in the region 1111, a criterion for providing thesize of the circle according to the driving record may represent thenumber of times of events in a total of three sizes. As an example, thefirst number of times or more (e.g., 5 times) may be displayed by thelargest circle, the second number of times (e.g., between 2 and 4 times)may be displayed by a medium circle, and the third number of times(e.g., less than 1 time) may be displayed by the smallest circle.

However, the circular display of driving information in the region 1111is only an example of the present invention, but the present inventionis not limited thereto. For example, the driving information may also bedisplayed through other polygons such as squares or visual bubbles suchas balloons. According to another exemplary embodiment of the presentinvention, the driving record information may be displayed whilemaintaining the above criteria through a rod shaped method (e.g., alarge rod/medium rod/small rod), not the circular method.

FIGS. 13A to 13C are user interface diagrams illustrating a refreshprocess of the main user interface according to an exemplary embodimentof the present invention. As illustrated in FIG. 13A, the user may inputan up and down flick operation 1201 that descends top to bottom throughthe main user interface.

In this case, the user terminal device 400 may display an icon 1202indicating that the main user interface is being refreshed asillustrated in FIG. 13B.

In addition, if the refresh is completed, the user terminal device 400may update and display information displayed on the main user interfacewith information of a current time point as illustrated in FIG. 13C.

FIGS. 14A to 14B are user interface diagrams illustrating a black boxregistration process through the main user interface according to anexemplary embodiment of the present invention. As illustrated in FIG.14A, the user may select a region 1301 displaying information of theconnected black box. In this case, the user terminal device 400 maydisplay a registered black box list 1302 as a pop-up window asillustrated in FIG. 14B, and may display a currently connected black box“QXD 3000” at the top. Here, the display through the pop-up window maybe performed only when there are two or more registered devices.

If the user selects a device other than the currently connected imagecapturing apparatus in the black box list 1302, the pop-up window may beclosed after connecting to the device selected by the user.

FIGS. 15A to 15B are diagrams illustrating a user interface of a lastparking location according to an exemplary embodiment of the presentinvention. If a parking elapsed time icon 1106-5 illustrated in FIG. 12Ais selected, the user terminal device 400 may display a user interface1401 that displays the last parking location of the vehicle on a map, asillustrated in FIG. 15A. FIG. 15A illustrates that the last parkinglocation of the vehicle is displayed on the map in the form in which avehicle icon is included in the form of a visual bubble. In addition, inan upper region 1402 of the user interface 1401, parking location,parking time, and parking elapsed time information of the vehicle may bedisplayed.

In addition, as illustrated in FIG. 15B, the user interface 1401 mayprovide the last parking location and an image 1403 for the last parkinglocation. Here, the image 1403 for the last parking location may be animage captured at a predetermined time point during a switching periodwhen the black box 100 is switched from the normal mode to the parkingmode according to the starting off after the parking of the vehicle iscompleted.

In addition, the map displayed on the user interface 1401 may receivevarious touch inputs such as tap/drag/zoom in/zoom out/rotation from theuser.

Meanwhile, a region 1404 is a parking history button, and when theregion 1404 is selected, a parking history user interface may bedisplayed. This will be described below with reference to FIG. 16 .

In addition, a region 1405 is an image download button, and when theregion 1405 is selected, a corresponding image may be stored in the userterminal device 400.

In addition, a region 1408 is a button that displays a current locationof the user and the last parking location of the vehicle, and when theregion 1408 is selected, the current location of the user and the lastparking location of the vehicle may be displayed on the map. This willbe described below with reference to FIG. 16 .

In addition, a region 1406 may be a shared button, and a region 1407 maybe a vehicle location display button. This will be described below withreference to FIGS. 17 and 18 .

Meanwhile, when there is no last parking location of the vehicle, theuser terminal device 400 may display a default location on the userinterface 1401. Alternatively, when there is a past parking location butno last parking location, the user terminal device 400 may display aprevious parking location on the user interface 1401.

FIG. 16 is a diagram illustrating a user interface displaying a user'scurrent location and a last parking location according to an exemplaryembodiment of the present invention. Referring to FIG. 16 , if the userselects a region 1501, the user terminal device 400 displays the currentlocation of the user and the last parking location of the vehicle on themap, and may display a relationship between both locations by connectingthe current location of the user and the last parking location of thevehicle in a straight line (dotted line).

In addition, when displaying the straight line connecting the currentlocation of the user to the last parking location of the vehicle, theuser terminal device 400 may control a scale of the map so that the lastparking location of the vehicle and the current location of the user aredisplayed on one screen.

In addition, although not illustrated in FIG. 16 , the user terminaldevice 400 may calculate a straight line distance between the currentlocation of the user and the last parking location of the vehicle and adistance via a driveable road at the same time as the straight linedisplay, and may also display the calculated distance on the screen. Inaddition, the user terminal device 400 may perform route guidance fromthe current location of the user to the last parking location of thevehicle by interworking with a navigation application.

FIGS. 17A to 17C are user interface diagrams illustrating a process forsharing a last parking location image according to an exemplaryembodiment of the present invention. As illustrated in FIG. 17A, when aregion 1602 corresponding to a share button is selected in a userinterface 1601, the user terminal device 400 may display a sharing typeselection pop-up window 1603 as illustrated in FIG. 17B.

If the user selects “Share my car image” in the sharing type selectionpop-up window 1603, the user terminal device 400 may display a shareableimage list screen illustrated in FIG. 17C. Here, the shareable imagelist screen may include a front image list 1605 and a rear image list1606, and the user may select an image to share from the displayedshareable image list screen.

If the user selects an image to share and selects a share button 1607,the user terminal device 400 may display a shareable social networkservice (SNS) list or a contact list.

FIGS. 18A to 18E are user interface diagrams illustrating a process forsharing a last parking location according to an exemplary embodiment ofthe present invention. As illustrated in FIG. 18A, when a share button1702 is selected in a user interface 1701, the user terminal device 400may display a sharing type selection pop-up window 1703 as illustratedin FIG. 18B.

If the user selects “Share my car location” in the sharing typeselection pop-up window 1703, the user terminal device 400 may display ascreen for sharing the last parking location of my car illustrated inFIG. 18C. Here, in FIG. 18C, the last location of my car may bedisplayed in the center of the map, and an address of the last parkinglocation may be displayed at the top of the screen. In this case, if theuser selects “Share” 1705, the user terminal device 400 may display ashareable application list 1706 illustrated in FIG. 18D. Here, theshareable application is a list of applications that may share locationinformation among applications installed in the user terminal device400, and in the list 1706, icons and application names may be displayed.

If the user selects an application from the shareable application list1706, the user terminal device 400 may generate sharing information andshare the sharing information through the selected application.

In this case, the sharing information displayed when sharing the lastparking location may be as illustrated in FIG. 18E. That is, sharinginformation 1707 may include an image displaying the last parkinglocation of the vehicle on a map, and a link URL of the correspondingmap.

As an example, when the sharing information 1707 is shared through amessage, a terminal device of another user may display the sharinginformation through the message, and when another user selects thesharing information, the last parking location of the user may bedisplayed on the map.

FIGS. 19A to 19C are diagrams illustrating a user interface for managingparking history according to an exemplary embodiment of the presentinvention. A region 1802 displayed on a user interface 1801 of FIG. 19Ais a parking history button, and if the user selects the region 1802,the user terminal device 400 may display a user interface 1803 asillustrated in FIG. 19B.

The user interface 1803 may provide parking location information andparking date and time information in the latest parking record order. Inthis case, the user interface 1803 may not provide the last parkinglocation information displayed on the user interface 1801 as a parkinghistory.

If one parking history is selected in the user interface 1803, a mapuser interface 1805 may be displayed to be unfolded at the bottom of theselected parking history as illustrated in FIG. 19C. In this case, themap user interface 1805 may display a parking location imagecorresponding to the selected parking history and a parking location onthe map. Here, the touch interaction on the map may be applied in thesame way as the map interaction described above.

FIGS. 20A to 20B are diagrams illustrating a user interface for managingparking history according to an exemplary embodiment of the presentinvention. Referring to FIG. 20A, in a user interface 1901 indicatingthe parking history list, when the user maintains a touch and inputsleft flicking to move from left to right, a delete button 1902 for aparking history to which the left flicking is input may be activated asillustrated in FIG. 19B. If the user selects the delete button 1902, theparking history selected in the parking history list may be deleted.

FIGS. 21A to 21B are diagrams illustrating a user interface for managingparking history according to an exemplary embodiment of the presentinvention. Referring to FIG. 21A, in a user interface 2001 indicatingthe parking history list, when the user inputs a touch & hold command tomaintain a touch for a predetermined time after inputting a touch, theuser terminal device 400 may display a parking history list editing userinterface 2003 as illustrated in FIG. 21B.

If the user selects a whole button in the user interface 2003,checkboxes of all lists are selected, and if the whole button isselected again in the state in which all the lists are selected, thecheckboxes of all the lists may be deselected.

In addition, when the user selects a checkbox in the user interface2003, the corresponding check box is checked and a delete button may beactivated at the bottom. In addition, when the user selects a listdelete button, the selected list may be deleted.

FIGS. 22A to 22D are diagrams illustrating a user interface in asituation of an impact event of the vehicle or a movement event of thevehicle according to an exemplary embodiment of the present invention.As illustrated in FIG. 22A, the main user interface may display animpact notification icon notifying the occurrence of an impact event forthe vehicle when an impact event occurs while parking or driving thevehicle on the image of the vehicle. Alternatively, as illustrated inFIG. 22B, when a movement of the vehicle is detected while parking thevehicle, the main user interface may display a visual object (e.g., anarrow icon) notifying the movement event of the vehicle on the image ofthe vehicle.

If the user selects a vehicle image object in the main user interface,the user terminal device 400 may display an event history list 2101 asillustrated in FIG. 22C. Here, the event history list 2101 may displayevent information for each event, and the event information may displayan event location, an event date, and an event time.

In addition, the event history list 2101 may position and displayinformation on the latest occurrence event at the top.

In addition, the event history list 2101 may display an event type icon2102. Here, the event type icon 2102 may display an impact event duringparking, a movement event during parking, and an impact event duringdriving to be distinguished by different icons.

In addition, the event history list 2101 may include a region 2103corresponding to a remote playback button. Here, the region 2103 mayprovide a notification that occurred within a predetermined period froma current time point. Here, the “remote play” may be a function toprovide an image corresponding to the selected notification in the blackbox 100, not the user terminal device 400.

However, the “remote playback” is not limited thereto, and may beimplemented to provide the image corresponding to the selectednotification in the user terminal device 400. In this case, consideringthe size of a user data storage space allocated to the server 300, adata transmission rate, and the like, it is possible to provide imageinformation for an event that occurred during a predetermined period.

If the region 2103 is selected in a situation in which the operationmode of the black box 100 is a normal recording mode, the black box 100may play the corresponding image after the end of the normal recordingmode. Alternatively, if the region 2103 is selected in a situation inwhich the operation mode of the black box 100 is a parking recordingmode, the remote playback in the black box 100 may not be possible.

Meanwhile, when one event is selected by the user in the event historylist 2101, the user terminal device 400 may display a user interface2104 as illustrated in FIG. 22D.

If the event is the impact event, the user interface 2104 may displayimpact occurrence location and impact occurrence time information in anupper region. Alternatively, if the event is the movement event duringparking, the user interface 2104 may display movement detection locationand movement detection time information in the upper region.

In addition, the user interface 2104 may display an image 2105 capturedat the event location. Here, the image 2105 may be a motion imagegenerated by combining at least two images between a predetermined timebefore the event occurrence and a predetermined time after the eventoccurrence. At this time, in order to visually indicate that the eventhas occurred, the image 2105 may be displayed to vibrate left and rightor up and down to move, or may be displayed using a vibration animationmethod. The image 2105 may be displayed using various visual designelements such as a rectangle, square, circle, water drop, bubble, andthe like.

In addition, an image download button may be provided in one region ofthe image 2105. If the user selects the image download button, thecorresponding image may be stored in the user terminal device 400.

In addition, the user interface 2104 may display an event occurrencelocation on a map, and the map may receive a touch interaction such astap/drag/zoom in/zoom out/rotation.

FIGS. 23A to 23C are diagrams illustrating a user interface wheninputting a live command according to an exemplary embodiment of thepresent invention. As illustrated in FIG. 23A, a main user interface mayinclude a region 2201 corresponding to a live button. Here, the livebutton may be a button that requests an image captured in real time fromthe black box 100 of a vehicle being parked.

If the user selects the region 2201 corresponding to the live button inthe main user interface, a user interface 2202 as illustrated in FIG.23B may be displayed.

Here, the user interface 2202 may include a region 2203 displayingparking information at the top, and in the region 2203, the last parkinglocation and a live command request time point may be displayed.

In addition, the user interface 2202 may display a pop-up window 2204related to providing the live image. Here, the pop-up window 2204related to providing the live image may be located on the top of thecurrent vehicle location displayed on the map.

Since the amount of data is limited due to the characteristics oflow-power wide-area wireless communication, the number of times the liveimage may be used may be predetermined, and the pop-up window 2204 maydisplay information on the number of times of possible live images. Asan example, the pop-up window 2204 may display information on the numberof uses of live images that the user may use when the number of times oflive images that the user may still use remains, and may provide aphrase such as “the number of uses of the month has been exceeded” whenthe number of uses of the live images has been exceeded.

Meanwhile, when the pop-up window 2204 is selected, the user terminaldevice 400 may display a live image 2205 as illustrated in FIG. 23C.Here, the live image 2205 is an image captured in real time in the blackbox 100 operating in the parking recording mode, and may be a motionimage generated by combining at least two images after a request timepoint through the live image button 2201 or a video acquired in realtime from the black box 100 upon request. If the user selects a downloadbutton 2206 disposed in one region of the live image 2205, thecorresponding image may be stored in the user terminal device 400.

Meanwhile, the user interface 2202 may include a share button 2206 thatoperates in the same manner as the above-described share button and avehicle location display button 2207 that operates in the same manner asthe above-described vehicle location display button.

Meanwhile, the user interface 2202 may include a live image historyregion 2208 at the top. If the user selects the live image historyregion 2208, the user terminal device may display a live image historymanagement user interface. This will be described in more detail withreference to FIGS. 24A to 24B.

FIGS. 24A to 24B are user interface diagrams illustrating live historyimage management according to an exemplary embodiment of the presentinvention. If the user selects the region 2208 illustrated in FIG. 23B,the user terminal device may display a live image history managementuser interface as illustrated in FIG. 24A. Here, live requested locationand time information may be displayed on a live image history list.

If the user selects one from the live image history list and thenselects a more viewing object 2302 on the right, a user interfaceincluding a live image, a map, and a location corresponding to theselected list may be displayed at the bottom of the selected list asillustrated in FIG. 24B.

FIGS. 25A to 25F are user interface diagrams illustrating a method forswitching an image display according to an exemplary embodiment of thepresent invention. As described above, if the last parking locationrequest, the live image request, the event confirmation request, or thelike is input from the user, the user terminal device 400 may display auser interface including a map indicating the location of the vehicleand an image captured in the black box 100, as illustrated in FIG. 25A.

If the user touches the image 2401, the user terminal device 400 maydisplay an image viewing screen illustrated in FIG. 25B. In addition,when the user touches the image viewing screen illustrated in FIG. 25B,the user terminal device 400 may display a screen capable of receivingvarious user inputs, such as screen closing, screen switching, and imagedownload, as illustrated in FIG. 25C.

In addition, when the user rotates the terminal device 400 from avertical direction to a horizontal direction in a state in which theimage viewing screen illustrated in FIG. 25B is displayed, the userterminal device 400 may rotate and enlarge the image viewing screen asillustrated in FIG. 25D to display the image viewing screen.Alternatively, when the user selects a screen switch icon disposed inthe upper right in a state in which the image viewing screen illustratedin FIG. 25C is displayed, the user terminal device 400 may rotate andenlarge the image viewing screen as illustrated in FIG. 25E to displaythe image viewing screen.

Meanwhile, each image displayed on the image viewing screen may receivevarious user operations. As an example, as illustrated in FIG. 25F, theimage may be enlarged or reduced according to a pinch zoom in/outoperation of the user. That is, if the user inputs the pinch zoom inoperation that selects two points of the image and collects the twopoints inward, the image may be reduced, and if the user inputs thepinch zoom out operation that selects the two points of the image andspreads the two points outward, the image may be enlarged.

FIGS. 26A to 26B are diagrams illustrating an environment setting userinterface according to an exemplary embodiment of the present invention.Referring to FIG. 26A, an environment setting user interface 2501 mayinclude a member information region, a service period region, anotice/event region, a coupon service region, a device managementregion, an emergency SOS notification region, a cloud safety alertregion, and a my driving region.

Here, the coupon service region may display information on the number ofcoupons available to the user. In addition, when a coupon serviceconfirmation region 2502 of the environment setting user interface 2501is selected, the user terminal device 400 may display a coupon list 2503as illustrated in FIG. 26B.

Here, the coupon list 2503 may display coupons assigned to the user, thecoupon list 2503 may be configured with a plurality of coupon items, andeach coupon item may display a coupon icon, a coupon name (e.g., washerfluid, wiper, etc.), a coupon provision condition (e.g., provided whenvisiting a dealer, etc.), a coupon usage period, and a coupon status.Here, the coupon status may include “Use” indicating that the coupon iscurrently available, “To be provided” indicating that the coupon is tobe provided, “Use completed” indicating that the coupon has been used,and “Period expired” indicating that the coupon has expired.

In addition, the arrangement order of the coupon items may be displayedfrom top to bottom in the order of available, to be available, to beprovided, use completed, and period expired.

In addition, whether to activate information displayed on the couponitem may be adjusted according to the status of the coupon. As anexample, the currently available coupons may be displayed by activatingall text and all icons.

In addition, coupons to be provided may be displayed by activating alltext and all icons, but deactivating only a “to be provided button”. Inaddition, coupons of which use has completed may be displayed bydeactivating all text and icons except for the “use completed stampicon”. In addition, coupons of which use period has expired may bedisplayed by deactivating all text and icons except for a “periodexpired stamp icon”.

According to the present invention, the user may perform payment usingthe coupon through a user terminal device 400 before visiting the dealeror in the vehicle.

FIGS. 27A to 27C are diagrams illustrating a user interface illustratinga coupon usage process according to an exemplary embodiment of thepresent invention. When the user selects the use of a specific couponfrom a coupon list 2601 illustrated in FIG. 27A, the user terminaldevice 400 may display a coupon available dealer list 2602 asillustrated in FIG. 27B.

Here, the number of dealers exposed in the coupon available dealer list2602 may be displayed up to 10 in a close order within a predeterminedradius (e.g., around 50 km) based on the user's current location.

If there is no available dealer within the predetermined radius based onthe user's current location, the user terminal device 400 may display atleast one of the nearest dealers out of the predetermined radius.

In addition, in each dealer item of the coupon available dealer list2602, a dealer name, an address, a phone number, a route guidancebutton, and distance information based on the current location may bedisplayed. If the user selects the phone number, a call application maybe called in a state in which the corresponding number is pre-inputted.

In addition, if the user selects the route guidance button, the userterminal device 400 may display a route guidance screen guiding a routefrom the current location to the dealer. This will be described in moredetail with reference to FIGS. 28A to 28C.

FIGS. 28A to 28C are diagrams illustrating a user interface for guidinga route to a coupon available dealer according to an exemplaryembodiment of the present invention. Referring to FIG. 28A, if the userselects a route guidance button from a coupon available dealer list2701, the user terminal device 400 may display a user interface 2702indicating a location of a dealer on a map as illustrated in FIG. 28B.

If the user selects “Find directions” in the user interface 2702, theuser terminal device 400 may display a user interface 2703 asillustrated in FIG. 28C. Here, the user interface 2703 may be a searchroute guidance user interface that displays a plurality of routes (e.g.,a recommendation route and a fast route) from a user's current locationto a selected dealer. If the user selects one of the plurality of routesin the user interface 2703, the user terminal device 400 may display aroute guide screen guiding to the selected route.

FIGS. 29A to 29B are user interface diagrams illustrating an emergencySOS notification setting process according to an exemplary embodiment ofthe present invention. If the user selects an “emergency SOSnotification region” in an environment setting user interfaceillustrated in FIGS. 29A to 29B, the user terminal device 400 maydisplay an emergency contact management user interface 2801 illustratedin FIG. 29A. Here, the emergency contact management user interface 2801may display pre-registered emergency contact information.

If the user selects a setting icon of the user interface 2801, the userterminal device 400 may display a list pop-up window 2802 illustrated inFIG. 29B. In addition, the user may input a command such as a namechange, a number change, or a contact deletion through the list pop-upwindow 2802.

FIGS. 30A to 30C are user interface diagrams illustrating an emergencySOS contact registration process according to an exemplary embodiment ofthe present invention. Referring to FIGS. 30A to 30C are user interfacediagrams, if there is no pre-registered emergency contact information,the user terminal device 400 may display a user interface 2901 asillustrated in FIG. 30A. If the user selects a “new contactregistration” region of a user interface 2901, the user terminal device400 may display a user interface 2902 for SOS contact direct input asillustrated in FIG. 30B.

That is, the user interface 2902 for SOS contact direct input mayinclude an emergency contact name and phone number input region, andwhen the user selects “register”, the corresponding contact may beregistered as an SOS contact.

In this case, the user terminal device 400 may generate a message to betransmitted to the emergency SOS contact for confirmation of a newlyregistered emergency SOS contact, and may transmit the generated messageto a terminal device corresponding to the registered emergency SOScontact. In this case, the terminal device corresponding to theemergency SOS contact may receive and display a text message asillustrated in FIG. 30C.

Meanwhile, according to the emergency SOS contact registration processof FIGS. 30A to 30C are user interface diagrams described above, it hasbeen described as an example that the user directly inputs the contactname of the user and the contact thereof, but is not limited thereto.According to another exemplary embodiment of the present invention, the“connected service application” may display a list of pre-registeredcontacts by interworking with a pre-installed contact application on theuser terminal device 400, and the user may register the emergency SOScontact by selecting at least one contact to be registered as theemergency SOS contact from the pre-registered contact list.

FIGS. 31A to 31B are user interface diagrams illustrating a processingscenario when an emergency situation occurs according to an exemplaryembodiment of the present invention. Here, the emergency situationaccording to the present invention means a more serious emergencysituation than the occurrence of a general impact event or a movementevent, and may mean, for example, an accident event occurrence situationcorresponding to an impact occurrence greater than a predeterminedimpact value.

If the impact value greater than a predetermined impact value isdetected in the black box 100, the black box 100 may transmit anemergency situation event to the server 300, and the server 300 mayinform the user terminal device 400 that it is the emergency situation.In this case, the user terminal device 400 may detect a pre-registeredemergency SOS contact and create an emergency notification message to betransmitted to the emergency SOS contact. In addition, the user terminaldevice 400 may transmit the created emergency situation notificationmessage to a pre-registered emergency SOS contact.

FIG. 31A is an example of an emergency notification message transmittedto an emergency SOS contact. Referring to FIG. 31A, an emergencysituation notification message 3001 may include an emergency comment, adriver's phone number, an accident time and location, a URL capable ofconfirming an accident occurrence location, a sound source URL recordedin an accident process, and a link address for confirming an accidentimage.

In addition, the emergency situation notification message 3001 mayfurther include a preview of the accident occurrence location, and whenselecting a preview, it is possible to enter a map screen that displaysthe preview in detail.

If the recipient of the emergency situation notification message selectsa URL that may confirm the accident occurrence location included in themessage, the terminal device may display a user interface 3002indicating an accident location as illustrated in FIG. 31B. Here, theuser interface 3002 may include a region 3003 that displays vehiclelocation of a time point at which the impact occurs and time informationthat the impact occurs. In addition, the user interface 3002 may includea map region that displays the location of the vehicle where the impacthas occurred on the map. In addition, the user interface 3002 mayinclude a vehicle location display button 3005.

On the other hand, if the recipient of the emergency situationnotification message selects the recorded sound source URL included inthe message, the terminal device may playback the sound source recordedin the accident process.

In addition, if the recipient of the emergency situation notificationmessage selects the URL for confirming the emergency situation imageincluded in the message, the terminal device may access a URL addressthrough a communication network and playback the image obtained in theemergency situation.

FIG. 32 is a diagram illustrating an example of a push notificationaccording to an exemplary embodiment of the present invention. Accordingto an exemplary embodiment of the present invention, the user terminaldevice 400 may receive notifications of various events from the server300, and may display the received notification information on the screenin the form of a push message.

As an example, referring to FIG. 32 , the push notification may includevarious notifications such as a “notification of impact occurrence whiledriving”, a “notification of impact image upload completion”, a“notification of vehicle movement detection”, a “notification ofrecommendation of popular places around a destination”, a “notificationof weather/atmosphere information”, a “notification of batterylow-voltage”, a “notification of switching to driving state”, a“notification of parking impact occurrence”, and a “notification ofblack box power on/off.

Here, the “notification of impact occurrence while driving” means anotification that is displayed when an impact occurs to a vehicle whiledriving. If the user selects the “notification of impact occurrencewhile driving”, the user terminal device 400 may execute the connectedservice application and display the impact notification history screenillustrated in FIG. 22C.

In addition, the “notification of impact image upload completion” meansa notification that is displayed when the impact image upload iscompleted.

In addition, the “notification of vehicle movement detection” means anotification that is displayed when the vehicle movement detectionoccurs while parking. If the user selects the “notification of vehiclemovement detection”, the user terminal device 400 may execute theconnected service application and display the impact notificationhistory screen illustrated in FIG. 22C.

In addition, the “notification of popular places around a destination”means a notification that is displayed when the vehicle arrives at thedestination. If the user selects the “notification of popular placesaround a destination”, the user terminal device 400 may execute theconnected service application and display the popular places around theuser's destination. In this case, the popular places may be popularplaces selected based on preference information pre-registered for theuser.

In addition, the “notification of parking impact occurrence” means anotification that is displayed when a parking impact occurs. If the userselects the “notification of parking impact occurrence”, the userterminal device 400 may execute the connected service application anddisplay the impact notification history screen illustrated in FIG. 22C.

In addition, the “notification of weather/atmosphere information” maymean a notification that guides a surrounding weather and/or atmospherestatus. Here, the “notification of weather/atmosphere information” maybe displayed as a phrase that guides the surrounding weather and/oratmosphere status.

Specifically, the “notification of weather/atmosphere information” maybe displayed when it is detected that a surrounding fine dustconcentration is not good. As an example, when the surroundings of thevehicle have a fine dust concentration corresponding to “bad” or higher,the notification may be displayed in the form of a phrase such as “Thefine dust concentration is bad. Close the window tightly and switch anair conditioner to indoor circulation”.

In addition, the “notification of weather/atmosphere information” may bedisplayed when it is detected that a surrounding yellow dustconcentration is not good. As an example, when the surroundings of thevehicle have a yellow dust concentration corresponding to “bad” orhigher, a corresponding notification may be displayed, and thenotification may be displayed in the form of a phrase/sentence.

In addition, the “notification of weather/atmosphere information” may bedisplayed when the air has improved after a notification of a warning offine dust/yellow dust in the area while driving. As an example, if theair has improved after the notification of the warning of fine dust inthe area while driving, the notification may be provided in a text form,such as “The surrounding air has become pleasant. Please open the windowto ventilate the indoor air”. As another example, if the air in the areais good while driving the vehicle, the notification may be provided in atext form, such as “The surrounding air is pleasant. Please open thewindow to ventilate the indoor air.”

In addition, the “notification of weather/atmosphere information” maygenerate and provide a notification based on current time informationand driving/parking status information of the vehicle. As an example, ifthe black box is in the parking mode and there is news that it israining before a user's work time (here, the work time may be a resultvalue learned through learning about the user's work time), thenotification may be provided in the form of a guide phrase such as“There is news that it is raining today, so be sure to bring a smallumbrella and pay more attention to safe driving”. In addition, if thereis news that it is snowing, the notification may be provided in the formof a guide phrase such as “There is news that it is snowing today, so besure to bring a small umbrella and pay more attention to safe driving”.In addition, if there is news that it is raining and snowing, thenotification may be provided in the form of a guide phrase such as“There is news that it is raining and snowing today, so be sure to bringa small umbrella and pay more attention to safe driving”.

As another example, if the black box is switched from the driving modeto the parking mode after starting off on weekdays, and there is newsthat it is raining, the notification may be provided in the form of aguide phrase such as “There is news that it is raining, so we recommendindoor parking today”. In addition, if there is news that it is snowing,the notification may be provided in the form of a guide phrase such as“There is news that it is snowing, so we recommend indoor parkingtoday”.

As another example, if the black box is in parking mode before a user'sweekend start-on time (where the time may be a value learned accordingto a user's weekend behavior pattern) and there is no news that it issnowing or raining within 7 days from the day, the notification may beprovided in the form of a guide phrase such as “There is no news that itwill be raining for a while. This weekend is a good day to wash the car”or “There is no news that it will be snowing and raining for a while.This weekend is a good day to wash the car”.

In addition, the “notification of vehicle battery low voltage” is tonotify the vehicle battery low voltage, and if the user selects the“notification of vehicle battery low voltage”, the user terminal device400 may execute the connected service application and display the mainuser interface.

In addition, the “notification of black box power off” is to notify theblack box power off, and if the user selects the “notification of blackbox power off”, the user terminal device 400 may execute the connectedservice application and display the main user interface.

Here, the case in which the “notification of black box power off” isnotified may include a case in which the black box 100 becomes a lowvoltage block setting value and is automatically turned off, a case inwhich the user arbitrarily turns off the black box, a case in which theblack box is turned off by unplugging a power cord of the black box, anda case in which the power is turned off by a timer setting.

In addition, the “notification of black box power on” is to inform thatthe power of the black box is turned on, and if the user selects the“notification of black box power on”, the user terminal device 400 mayexecute the connected service application and display the main userinterface.

Additionally, although not illustrated in FIG. 32 , the pushnotification according to an exemplary embodiment of the presentinvention may further include “notification of membership usecompletion”.

The “notification of membership use completion” is to notify a couponservice usage history through a mobile barcode, and if the user selectsthe “notification of membership use completion”, the user terminaldevice 400 may execute the connected service application and display amembership usage history screen.

FIGS. 33A to 33F are diagrams illustrating a user interface for a remoteplayback request in a normal recording mode state of a black boxaccording to an exemplary embodiment of the present invention. The usermay select a “remote playback button” in an event history list 3201illustrated in FIG. 33A or in an event impact notification userinterface 3202 illustrated in FIG. 33B. Here, the remote playback button3202 may be a button that receives a user input requesting a black boxto play an image corresponding to an event selected in the event historylist 3201 or an event displayed on the user interface 3202.

If the operation mode of the black box 100 is the normal recording modestate, the user terminal device 400 may display a pop-up window 3203inquiring whether to request the black box 100 to play the correspondingimage, as illustrated in FIG. 33C or FIG. 33D.

If the user selects “Yes” in the pop-up window 3203, the user terminaldevice 400 may display a message 3204 guiding that the playback of thecorresponding image is requested to the black box as illustrated in FIG.33E or FIG. 33F.

FIG. 34 is a diagram illustrating a remote playback scenario in thenormal recording mode state of the black box according to an exemplaryembodiment of the present invention. Referring to FIG. 34 , when theuser requests the remote playback of the image through the userinterface illustrated in FIGS. 33A to 33F, the server 300 may transmitthe playback request of the corresponding image to the black box 100(3301).

In this case, the black box 100 may display a pop-up window 3302indicating that image playback is requested in the connected serviceapplication of the user terminal device 400, and simultaneously output avoice informing the image playback request.

If the user selects “Cancel” in the pop-up window 3302, the black box100 may display a live view image corresponding to the image currentlybeing captured through a camera.

However, when the user selects “OK” in the pop-up window 3302, the blackbox 100 may determine whether the image requested by the user terminaldevice 400 is stored in the black box 100 (3303), and may play thecorresponding image (3304) if there is the corresponding image (3303:Y). In addition, after the playback of the corresponding image ends, theblack box 100 may display a live view image (3305).

However, if there is no corresponding image (3303: N), a pop-up window3306 indicating that there is no corresponding image may be displayed,and the user may select OK in the pop-up window 3306 or display the liveview image after a preset time elapses (3307).

FIG. 35 is a diagram illustrating an operation scenario of a black boxwhen an additional playback request is received during image playbackaccording to an exemplary embodiment of the present invention. Referringto FIG. 35 , the black box 100 may display a pop-up window 3401indicating that image playback is requested in the connected serviceapplication of the user terminal device 400, and simultaneously output avoice informing the image playback request. If the user selects “OK” inthe pop-up window 3401, the black box 100 may determine whether theimage requested by the user terminal device 400 is stored in the blackbox 100, and may play the corresponding image if there is thecorresponding image.

On the other hand, if a playback request of another image is requestedin the connected service application of the user terminal device 400during the playback of the corresponding image (3402), the black box maydisplay a pop-up window 3402 indicating that the playback of anotherimage is requested in the connected service application of the userterminal device 400.

If the user selects “OK” in the pop-up window 3403, the black box 100determines whether the image requested from the user terminal device 400is the same image or a different image, and may play the same image(3404) when the image is the same image and may play the different image(3405) when the image is the different image.

FIGS. 36A to 36F are diagrams illustrating a user interface for a remoteplayback request in a parking mode state of the black box according toan exemplary embodiment of the present invention. The user may select a“remote playback button” in an event history list 3501 illustrated inFIG. 36A or in an event impact notification user interface 3502illustrated in FIG. 36B. Here, the remote playback button 3502 may be abutton that receives a user input requesting a black box to play animage corresponding to an event selected in the event history list 3501or an event displayed on the user interface 3502.

If the operation mode of the black box 100 is the normal recording modestate, the user terminal device 400 may display a pop-up window 3503inquiring whether or not to reserve the image playback after the blackbox 100 is switched from the parking recording mode to the normalrecording mode, as illustrated in FIG. 36C or FIG. 36D.

If the user selects “Yes” in the pop-up window 3503, the user terminaldevice 400 may display a message 3504 guiding that the playback of thecorresponding image is reserved in the black box as illustrated in FIG.36E or FIG. 36F.

FIG. 37 is a diagram illustrating an operation scenario of the black boxwhen the black box is switched from the parking mode state to the normalmode state according to an embodiment of the present invention.Referring to FIG. 37 , when the operation mode of the black box 100 isswitched from the parking recording mode to the driving recording mode(3601), the black box 100 may receive a reserved remote playback requestfrom the user terminal device 400 (3602). In this case, the black box100 may display a pop-up window 3603 indicating that image playback isrequested in the connected service application of the user terminaldevice 400, and simultaneously output a voice informing the imageplayback request. If the user selects “OK” in the pop-up window 3603,the black box 100 may determine whether the image requested by the userterminal device 400 is stored in the black box 100, and may play thecorresponding image if there is the corresponding image.

However, when the reserved remote playback request is received after aUSIM registration pop-up, the black box 100 may first display a USIMregistration pop-up window 3604. Thereafter, the black box 100 mayreceive the reserved remote playback request from the user terminaldevice 400 (3605), and may display a pop-up window 3606 indicating thatimage playback is requested in the connected service application of theuser terminal device 400, and simultaneously output a voice informingthe image playback request.

That is, when the remote playback request reserved by the user terminaldevice 400 is received before the USIM registration pop-up, the playbackrequest pop-up window may be displayed and the USIM registration pop-upwindow may not be displayed.

However, when the remote playback request reserved by the user terminaldevice 400 is received after the USIM registration pop-up, the playbackrequest pop-up window may be displayed after the USIM registrationpop-up window.

FIGS. 38A to 38B are diagrams illustrating a user interface forselecting a wireless communication network in a black box according toan exemplary embodiment of the present invention. The black box 100according to an exemplary embodiment of the present invention may accessthe server 300 using various wireless communication connection methods.As an example, the wireless communication connection method may bevarious, such as Long Term Evolution (LTE), Wireless Fidelity (WiFi),and Low-Power Wide-Area (LPWA).

The black box 100 may display a user interface capable of allowing theuser to select the wireless communication connection method according tothe type of a wireless communication module provided. If the userselects one wireless communication connection method through the userinterface, the black box 100 may transmit various data to the server 300using the selected wireless communication connection method. As anexample, when the black box 100 includes only an NB-IOT communicationmodule, the black box 100 may display a user interface as illustrated inFIG. 38A.

If the user selects the NB-IOT in the user interface as illustrated inFIG. 38A, the black box 100 may display a dongle registration userinterface as illustrated in FIG. 38B, and if the user selects “OK” inthe dongle registration user interface, a procedure for registering anNB-IOT dongle to the server 300 may proceed. Here, the procedure forregistering the NB-IOT dongle to the server 300 may be as describedabove in FIG. 5 .

According to such a procedure, the server 300 registration process ofthe communication module for wireless communication of the black box 100may be performed, and when an authentication of the communication moduleof the black box 100 is successful in the server 300 and registration iscompleted, the black box 100 may be connected to the server 300 bywireless communication.

FIGS. 39A to 39C are user interface diagrams illustrating a servicemember subscription process in a user terminal device according to anexemplary embodiment of the present invention. Referring to FIGS. 39A to39C, an interface for service member subscription may include a userinterface for inputting subscriber identification information. As anexample, referring to FIG. 39A, if the user selects “Member Subscription(3901)” displayed on a left interface, the user terminal device 400 mayswitch to an interface illustrated on the right for receiving asubscriber's ID (e-mail), a subscriber's password, a subscriber'snickname, and the like. If the user sees the screen displayed on thedevice 400 and enters the user identification information and selects“member registration (3902)”, the user terminal device 400 may transmitthe input user identification information to the server 300, and theserver 300 may determine whether the user is a user having a service useauthority to approve or reject the member subscription request. Thesubscriber identification information for which the member subscriptionrequest is approved may be stored in a subscriber information storageunit 321 of the server 300.

In addition, the interface for service member subscription may include auser interface for inputting identification information of the black box100 and/or the dongle 200 provided with the corresponding subscriber. Asan example, referring to FIG. 39B, if the user selects “DeviceRegistration (3903)” displayed on a left interface, the user terminaldevice 400 may switch to an interface illustrated on the right forreceiving a USIM serial number of the NB-IOT terminal 200 provided withthe user. If the user inputs the USIM serial number 3904 of the NB-IOTterminal 200 to the interface illustrated on the right and selects“Authentication Request (3905)”, the terminal device 400 may transmitthe input USIM serial number to the server 300, and the server 300 maydetermine whether the corresponding NB-IOT terminal 200 is a terminalhaving a service use authority to approve or reject the authenticationrequest. The apparatus identification information for which theauthentication request is approved may be stored in the subscriberinformation storage unit 321 of the server 300.

In this case, the server 300 may match and store the subscriberidentification information and the apparatus identification informationfor each of a plurality of service subscribers.

On the other hand, if the user's member subscription and terminalauthentication are completed according to the processes illustrated inFIGS. 39A and 39B, the user terminal device 400 may display a userinterface as illustrated in FIG. 39C. That is, as illustrated in FIG.39C, the serial number of the USIM of the dongle 200 authenticated tothe user may be displayed on one region 3906 of the user interface.

FIG. 40 is a timing diagram illustrating a method for providing aconnected service according to an exemplary embodiment of the presentinvention. FIG. 41 is a timing diagram illustrating a method forproviding a connected service according to another exemplary embodimentof the present invention.

Referring to FIG. 40 , the black box 100 may generate various dataduring an operation process and transmit the generated data to theserver 300 (S4001). Here, the data generated in the black box 100 may bevarious, such as image upload data, event occurrence notification data,location data, time data, and the like, and may be as described abovewith reference to FIGS. 5 to 11 .

In addition, the server 300 may store the data received from the blackbox 100 in a storage unit (S4002). As an example, the server 300 maystore the data received from the black box 100 in the service operationinformation storage unit 322.

In addition, the server 300 may search for identification information ofthe user terminal device 400 corresponding to the black box thatgenerated the data (S4003). As an example, the server 300 may search forthe identification information of the user terminal device 400corresponding to the black box 100 based on the information stored inthe service subscriber information storage unit 321.

In addition, the server 300 may generate a notification message to besent to the searched user terminal device 400 (S4004). Here, thenotification message is a message informing that data is generated inthe black box 100 and may be in a push message format.

Meanwhile, if the message is transmitted to the user terminal device 400(S4005), the user terminal device 400 may display the notificationmessage (S4006), and if the user selects the message, the user terminaldevice 400 may request the server 300 to provide the data generated inthe black box corresponding to the message (S4007).

In this case, the server 300 may transmit the black box datacorresponding to the request of the user terminal device 400 to the userterminal device 400 (S4008), and the user terminal device 400 mayconfigure a user interface based on the data generated in the black boxand display the user interface on the screen (S4009).

Meanwhile, FIG. 40 is one implementation example of the presentinvention, and may also be implemented as in FIG. 41 according toanother exemplary embodiment of the present invention. S4001 to S4002 ofFIG. 40 may be applied to FIG. 41 in the same way.

Specifically, the black box 100 may generate various data in theoperation process (S4101). In addition, the server 300 may store theblack box data generated from the black box received from the black box100 in the storage unit (S4102).

In addition, the server 300 may receive a service provision request fromthe user terminal device 400 (S4103). In this case, the server 300 maysearch for subscriber identification information corresponding to theuser terminal device 400 requesting the service provision from theservice subscriber information storage unit 321 (S4104), and may detectthe black box data corresponding to the subscriber identificationinformation from the service operation information storage unit 322 ifthere is searched subscriber identification information as a result ofthe search (S4105).

In addition, the server 300 may provide the type of detected black boxdata to the user terminal device 400 (S4106), and the user terminaldevice 400 may display the type of data as a visual object (S4107).

If the user of the user terminal device 400 requests the provision ofdata generated in the black box 100 by a click for the visual object ora voice command, the user terminal device 400 may transmits the blackbox data provision request to the server 300 (S4108), and the server 300may provide the black box data for the request to the user terminaldevice 400 (S4109).

In this case, the user terminal device 400 may configure a userinterface based on the black box data and display the user interface onthe screen (S4110).

According to the exemplary embodiment of the present invention, imagedata generated from a plurality of black boxes subscribed to the servicemay be separately stored according to the identification information ofthe black boxes. Accordingly, when an image data provision request isreceived from the user terminal device of the user corresponding to theidentifier of each black box in the future, the server may confirmwhether the image data to be provided exists and whether the request isan image data provision request from a legitimate user, by confirmingthe identifier of the user terminal device that has transmitted the dataprovision request.

Hereinafter, a method for providing a connected service according toanother exemplary embodiment of the present invention will be describedwith reference to the subsequent drawings.

FIG. 42 is a timing diagram illustrating a communication connectionprocess between a user terminal apparatus and a black box according toan exemplary embodiment of the present invention. Referring to FIG. 42 ,the user may execute the connected service application through the userterminal device 400 (S4201), and may select the “black box communicationconnection request” tab in the displayed user interface according to theexecution (S4202).

In addition, the user may select a black box model to be connected tocommunication among a plurality of black box models displayed on theuser interface (S4203). If there is only one registered black box, onlyone black box model may be displayed on the user interface.

In addition, the user may select one of a plurality of wirelesscommunication connection methods of the user terminal device 400(S4204). Here, the plurality of wireless communication connectionmethods may be various, such as Long Term Evolution (LTE), WirelessFidelity (WiFi), and WiFi hot spot.

In addition, the user terminal device 400 may access the server 300using the selected wireless communication connection method (S4205). Asan example, if the user selects Wi-Fi as the wireless communicationconnection method, the user terminal device 400 may access the server300 through a Wi-Fi network.

In addition, the user terminal device 400 may be communicativelyconnected to the user selection black box 100 through the accessedserver 300 (S4205). If the communication between the user terminaldevice 400 and the black box 100 is connected, the interface of the userterminal device 400 may display a visual object indicating that the userterminal device 400 accesses (S4206).

FIG. 43 is a diagram illustrating a main user interface of a userterminal device according to another exemplary embodiment of the presentinvention. Referring to FIG. 43 , a user interface may include aplurality of regions.

When one region 4301 of the user interface is selected, the userterminal device 400 may display a screen for configuring a connectedblack box or a new connection.

When a region 4302 of the user interface is selected, a screen fordisplaying and playing a recorded image of the black box 100 may bedisplayed.

When a region 4303 of the user interface is selected, black box productinformation may be displayed.

When a region 4304 of the user interface is selected, a main menu may bedisplayed.

When a region 4305 of the user interface is selected, a connectedservice menu may be displayed.

When a region 4306 of the user interface is selected, various menus foraccount settings, firmware updates, and safety cameras data may bedisplayed.

When a region 4307 of the user interface is selected, a screen forchanging a current communication connection type or disconnecting acurrent connection may be displayed. Here, a bar region included in theregion 4307 may display a communication connection method of the blackbox or a connection state of the black box (e.g., “Connected viaHotspot”).

When a region 4308 of the user interface is selected, a screen forshowing the connected WiFi network or adding a new network may bedisplayed.

When a region 4309 of the user interface is selected, a screen forsetting the settings of the black box may be displayed.

When a region 4310 of the user interface is selected, a screen fordisplaying a live image may be displayed.

When a region 4311 of the user interface is selected, variousnotification information, such as a firmware update notification, aGeo-Fencing zone entry and exit notification, and an impact notificationmay be displayed.

Hereinafter, a user interface for providing a connected serviceaccording to another exemplary embodiment of the present invention willbe described with reference to FIGS. 44 to 51 . The connected serviceillustrated in FIGS. 44 to 51 may be performed when the black box 100 isconnected to a wireless communication network, and the connected servicemay provide various services, such as a service showing the location ofthe vehicle, a service notifying that a vehicle enters or exits thegeo-fencing zone, and a service notifying that a strong impact isdetected.

FIGS. 44A to 44C are user interface diagrams illustrating an accountlogin process of a service subscriber according to an exemplaryembodiment of the present invention. When the user selects one region4401 of the main user interface illustrated in FIG. 44A, the userterminal device 400 may display a user interface of FIG. 44B. If theuser selects “sign in (4402)” in the user interface of FIG. 44B, theuser terminal device 400 may display a user interface of FIG. 44C.

In addition, if the user inputs the ID and password to a region 4403 ofFIG. 44C and selects “sign in (4404)”, the user terminal device 400 mayaccess the server 300 and perform log in. If the user's information isstored in the service subscriber information storage unit 321 of theserver 300, the server 300 may allow the user to log in.

FIGS. 45A to 45C are user interface diagrams illustrating a process ofdisplaying a location of a vehicle according to an exemplary embodimentof the present invention. When the user selects one region 4501 of themain user interface of FIG. 45A, the user terminal device 400 maydisplay a user interface of FIG. 45B.

The user interface of the FIG. 45B may display a location 4502 of theuser terminal device 400 on a map, and at the bottom of the map, a LiveView button capable of providing an image generated in the black box 100to the user is displayed. When the user clicks the Live View button, theimage provided from the black box 100 may be a real-time generatedimage, and may also be an image that is previously generated and storedin an internal memory of the server or the black box 100. In FIG. 45B,the Live View button is displayed on the bottom of the map, but this isonly an example, and the Live View button may be displayed on eitherside of the map screen or around the location 4502 displayed on the map.In addition, if the user selects the map of the user interface of FIG.45B, the user terminal device 400 may display a user interface of FIG.45C.

Here, the user interface of FIG. 45C is an interface that displays thelocation and direction 4503 of the vehicle on a map, and the interfacemay simultaneously display a location 4504 of the user terminal device400.

In addition, the user interface of FIG. 45C may display addressinformation 4505 corresponding to the location of the vehicle, anddisplay last information reception time information 4506 for thelocation of the vehicle.

FIGS. 46A to 46C are diagrams illustrating a process of setting whetherto notify geo-fencing according to an exemplary embodiment of thepresent invention. Here, geo-fencing means a technique for setting aradius based on a location information solution.

Specifically, when the user selects one region 4601 of the main userinterface of FIG. 46A, the user terminal device 400 may display a userinterface of FIG. 46B. In addition, if the user selects “pushnotification settings 4602” in FIG. 46B, the user terminal device 400may display a setting screen as illustrated in FIG. 46C.

In this case, the user may set a geo-fence notification 4603 through thesetting screen of FIG. 46C. Additionally, the setting screen of FIG. 46Cmay further include regions for setting Firmware Update Notification,Strong Impact Notification While Driving, Impact Notification WhileParked, and Strong Impact Notification While Parked.

FIGS. 47A to 47F are user interface diagrams illustrating a process ofsetting a geo-fencing area according to an exemplary embodiment of thepresent invention. When the user selects one region 4701 of the mainuser interface of FIG. 47A, the user terminal device 400 may display auser interface of FIG. 47B.

The user interface of FIG. 47B is a user interface that displays thelocation of the user terminal device 400 on a map, and when the userselects one region 4702 of the main user interface, the user terminaldevice 400 may display a user interface of FIG. 47C.

In addition, if the user selects “Set Geo-Fence (4703)” in the userinterface of FIG. 47C and selects a region 4704 in a user interface ofFIG. 47D, the user terminal device 400 may display a user interface asillustrated in FIG. 47E.

FIG. 47E illustrates a user interface for setting a geo-fencing area,and the user may set the geo-fencing area by first selecting a specificpoint 4705 on the map and selecting a radius distance 4706 centered onthe selected point. At this time, the set geo-fencing area may be set toa polygonal shape such as a circle or triangle, and the shape of thegeo-fencing area may be set according to user's input. In addition, theuser may set a notification 4707 when entering the geo-fencing area.

In this case, the user terminal device 400 may display a user interfacefor displaying the set geo-fencing area on the map as illustrated inFIG. 47F, and when the user selects a region 4708, the geo-fencing setmay be completed.

FIGS. 48A to 48C are user interface diagrams illustrating a process ofsetting a strong impact notification while driving a vehicle accordingto an exemplary embodiment of the present invention. Here, the strongimpact may mean a situation in which a large impact of a second impactlevel or more occurs, and a situation in which an impact that is greaterthan a first impact level and less than the second impact level occursmay be referred to as a general impact.

Specifically, when the user selects one region 4801 of the main userinterface of FIG. 48A, the user terminal device 400 may display a userinterface of FIG. 48B. In addition, if the user selects “pushnotification settings 4802” in FIG. 48B, the user terminal device 400may display a setting screen as illustrated in FIG. 48C.

In this case, the user may set a strong impact notification whiledriving through the setting screen of FIG. 48C.

FIGS. 49A to 49C are user interface diagrams illustrating a process ofsetting an impact notification while parking a vehicle according to anembodiment of the present invention. FIGS. 49A and 49B may be performedthrough the same processes as in FIGS. 48A and 48B, respectively.

In this case, the user may set an impact notification while parked 4901through the user interface of FIG. 49C.

FIGS. 50A to 50C are user interface diagrams illustrating a process ofsetting a strong impact notification while parking a vehicle accordingto an exemplary embodiment of the present invention. FIGS. 50A and 50Bmay be performed through the same processes as in FIGS. 48A and 48B,respectively.

In this case, the user may set a strong impact notification while parked5001 through a user interface of FIG. 50C.

FIGS. 51A to 51E are diagrams illustrating a process of checking animpact image according to an exemplary embodiment of the presentinvention. When the user selects one region 5101 of the main userinterface of FIG. 51A, the user terminal device 400 may display a userinterface of FIG. 51B.

The user interface of FIG. 51B is a user interface that displays thelocation of the user terminal device 400 on a map, and when the userselects one region 5102 of the user interface, the user terminal device400 may display a user interface of FIG. 51C.

In addition, if the user selects a cloud video 5103 in the userinterface of FIG. 51C and selects a driving impact video or a strongimpact video while parked in a user interface of FIG. 51D, the userterminal device 400 may display a user interface as illustrated in FIG.51E.

FIG. 51E illustrates a user interface for displaying an impact videolist, and the user may select a video to play on the displayed list andrequest a download. In this case, the user terminal device 400 maytransmit a transmission request of the selected video to the server 300and receive the selected video from the server 300.

Meanwhile, in the specification and the claims, terms such as “first”,“second”, “third”, “fourth”, and the like, if any, will be used todistinguish similar components from each other and be used to describe aspecific sequence or a generation sequence, but is not necessarilylimited thereto. The terms used as such will be understood by theexemplary embodiments of the invention described herein. Likewise, inthe case in which it is described herein that a method includes a seriesof steps, a sequence of the steps suggested herein is not necessarily asequence in which the steps may be executed, and any described step maybe omitted and/or any other steps that are not described herein may beadded to the method. For example, the first component may be referred toas a second component, and similarly, the second component may bereferred to as a first component, without departing from the scope ofthe present invention.

In addition, in the specification and the claims, terms such as “left”,“right”, “front”, “rear”, “top”, “bottom”, “over”, “under”, and the likedo not necessarily indicate relative positions that are not changed, butare used for explanation. It will be understood that these terms arecompatible with each other under an appropriate environment so thatexemplary embodiments of the present invention set forth herein may beoperated in a direction different from a direction illustrated ordescribed herein. The term. “connected” as used herein is defined asbeing connected directly or indirectly in an electrical ornon-electrical manner. Here, targets described as being “adjacent to”each other may physically contact each other, be close to each other, orbe in the same general range or region, in a context in which the abovephrase is used. Here, the present of the phrase “in an exemplaryembodiment” means the same exemplary embodiment, but is not necessarilylimited thereto.

In addition, in the specification and the claims, terms such as“connected”, “connecting”, “linked”, “linking”, “coupled”, “coupling”,and the like, and various modifications of these terms may be used asthe meaning including that one component is directly connected toanother component or is indirectly connected to another componentthrough the other component.

On the other hand, when it is mentioned that any component is “directlycoupled” or “directly connected” to another component, it is to beunderstood that any component may be coupled or connected to the otherelement without another component interposed therebetween.

In addition, terms “module” and “unit” for components used in thepresent specification are used only in order to easily make thespecification. Therefore, these terms do not have meanings or roles thatdistinguish from each other in themselves.

In addition, the terms used in the present specification are forexplaining exemplary embodiments rather than limiting the presentinvention. The singular expression used in the present specificationincludes the plural expression unless the context clearly indicatesotherwise. In the specification, it is to be noted that the terms“comprising” or “including”, and the like, are not be construed asnecessarily including several components or several steps described inthe specification and some of the above components or steps may not beincluded or additional components or steps are construed as beingfurther included.

Hereinabove, the present invention has been described with reference tothe exemplary embodiments thereof. All exemplary embodiments andconditional illustrations disclosed in the present specification havebeen described to intend to assist in the understanding of the principleand the concept of the present invention by those skilled in the art towhich the present invention pertains. Therefore, it will be understoodby those skilled in the art to which the present invention pertains thatthe present invention may be implemented in modified forms withoutdeparting from the spirit and scope of the present invention.

Therefore, the exemplary embodiments disclosed herein should beconsidered in an illustrative aspect rather than a restrictive aspect.The scope of the present invention is shown in the claims rather thanthe foregoing description, and all differences within the equivalentrange should be interpreted as being included in the present invention.

Meanwhile, the lane detection method according to various exemplaryembodiments of the present invention described above may be implementedas programs and be provided to servers or devices. Therefore, therespective apparatuses may access the servers or the devices in whichthe programs are stored to download the programs.

In addition, the method according to various exemplary embodiments ofthe present invention described above may be implemented as a programand stored in various non-transitory computer readable media andprovided. The non-transitory computer readable medium is not a mediumthat stores data for a short time such as a register, a cache, a memory,or the like, but means a machine readable medium that semi-permanentlystores data. Specifically, various applications or programs describedabove may be stored and provided in the non-transitory computer readablemedium such as a compact disk (CD), a digital versatile disk (DVD), ahard disk, a Blu-ray disk, a universal serial bus (USB), a memory card,a read only memory (ROM), or the like.

Although the exemplary embodiments of the present invention have beenillustrated and described hereinabove, the present invention is notlimited to the specific exemplary embodiments described above, but maybe variously modified by those skilled in the art to which the presentinvention pertains without departing from the scope and spirit of thepresent invention as claimed in the claims. These modifications shouldalso be understood to fall within the technical spirit and scope of thepresent invention.

What is claimed:
 1. A method for providing a connected service of animage capturing apparatus for a vehicle, the method comprising:connecting the image capturing apparatus for a vehicle to a server forproviding a connected service using a wireless communication module;generating event data including event code information and operationmode information of the image capturing apparatus for a vehicle, when anevent occurs in the image capturing apparatus for a vehicle; andtransmitting the generated event data to the server for providing aconnected service through the wireless communication module, wherein theevent includes a first event including at least one of an impactoccurrence event while parked, an impact occurrence event while driving,and a movement occurrence event while parked, the method furtherincludes extracting at least two images of images captured within apredetermined time range of an occurrence of the first event when thefirst event occurs, and generating image upload data using the extractedimages, and in the transmitting of the generated event data, the firstevent data and the image upload data are transmitted to the server forproviding a connected service through the wireless communication module.2. The method for providing a connected service of claim 1, wherein theimage upload data includes total image count information.
 3. A methodfor providing a connected service of an image capturing apparatus for avehicle, the method comprising: connecting the image capturing apparatusfor a vehicle to a server for providing a connected service using awireless communication module; generating event data including eventcode information and operation mode information of the image capturingapparatus for a vehicle, when an event occurs in the image capturingapparatus for a vehicle; and transmitting the generated event data tothe server for providing a connected service through the wirelesscommunication module, wherein the event includes a second eventincluding at least one of a parking location image request responseevent and a live image request response event according to a request inthe user terminal device provided with the connected service, the methodfurther includes extracting an image of a time point corresponding tothe second event when the second event occurs and generating imageupload data, and in the transmitting of the generated event data, thesecond event data and the image upload data are transmitted to theserver for providing a connected service through the wirelesscommunication module.
 4. The method for providing a connected service ofclaim 1, wherein the event includes a third event corresponding to anadvance driving assistance system (ADAS) event, and the method furtherincludes generating third event data including the type of the thirdevent, an occurrence time of the third event, and an occurrence locationof the third event, when the third event occurs.
 5. The method forproviding a connected service of claim 4, wherein the ADAS includes atleast two of a front vehicle start notification, a front vehiclecollision notification, and a lane departure notification.
 6. A methodfor providing a connected service of an image capturing apparatus for avehicle, the method comprising: connecting the image capturing apparatusfor a vehicle to a server for providing a connected service using awireless communication module; generating event data including eventcode information and operation mode information of the image capturingapparatus for a vehicle, when an event occurs in the image capturingapparatus for a vehicle; and transmitting the generated event data tothe server for providing a connected service through the wirelesscommunication module, wherein the method for providing the connectedservice further comprising: generating data for terminal registrationrequest of the image capturing apparatus for a vehicle upon initialconnection of the image capturing apparatus for a vehicle andtransmitting the generated data to the server for providing a connectedservice through the wireless communication module; and receivingregistration request response data including at least one of a trafficinformation day use time limit, a parking location image remainingcount, a live image remaining count, and an impact image remaining countfrom the server for providing a connected service as a response to theterminal registration request.
 7. The method for providing a connectedservice of claim 6, wherein the terminal registration request isrepeatedly performed whenever the power of the image capturing apparatusfor a vehicle is turned on.
 8. The method for providing a connectedservice of claim 1, wherein the wireless communication module is NB-IOTor CAT-M1.
 9. The method for providing a connected service of claim 1,wherein in the generating of the image upload data, the image capturingapparatus for a vehicle adjusts a size of data to be transmitted to theserver in consideration of data communication speed with the server forproviding a connected service, a state of a battery of the imagecapturing apparatus for a vehicle, and a size of a storage spaceallocated to the server for providing a connected service.
 10. An imagecapturing apparatus for a vehicle, comprising: a communication unitcommunicating with a server for providing a connected service; and acontrol unit generating event data including event code information andoperation mode information of the image capturing apparatus for avehicle, when an event occurs in the image capturing apparatus for avehicle, and controlling the communication unit to transmit thegenerated event data to the server for providing a connected service,wherein the event includes a first event including at least one of animpact occurrence event while parked, an impact occurrence event whiledriving, and a movement occurrence event while parked, the control unit:extracts at least two images of images captured within a predeterminedtime range of an occurrence of the first event when the first eventoccurs, and generates image upload data using the extracted images, andtransmits the first event data and the image upload data to the serverfor providing a connected service through the communication unit. 11.The image capturing apparatus for a vehicle claim 10, wherein the imageupload data includes total image count information.
 12. An imagecapturing apparatus for a vehicle, comprising: a communication unitcommunicating with a server for providing a connected service; and acontrol unit generating event data including event code information andoperation mode information of the image capturing apparatus for avehicle, when an event occurs in the image capturing apparatus for avehicle, and controlling the communication unit to transmit thegenerated event data to the server for providing a connected service,wherein the event includes a second event including at least one of aparking location image request response event and a live image requestresponse event according to a request in the user terminal deviceprovided with the connected service, the control unit: extracts an imageof a time point corresponding to the second event when the second eventoccurs and generates image upload data, and transmits the second eventdata and the image upload data to the server for providing a connectedservice through the communication unit.
 13. The image capturingapparatus for a vehicle claim 10, wherein the event includes a thirdevent corresponding to an advance driving assistance system (ADAS)event, and the control unit generates third event data including thetype of the third event, an occurrence time of the third event, and anoccurrence location of the third event, when the third event occurs. 14.The image capturing apparatus for a vehicle claim 13, wherein the ADASincludes at least two of a front vehicle start notification, a frontvehicle collision notification, and a lane departure notification. 15.An image capturing apparatus for a vehicle, comprising: a communicationunit communicating with a server for providing a connected service; anda control unit generating event data including event code informationand operation mode information of the image capturing apparatus for avehicle, when an event occurs in the image capturing apparatus for avehicle, and controlling the communication unit to transmit thegenerated event data to the server for providing a connected service,wherein the control unit controls to generate data for terminalregistration request of the image capturing apparatus for a vehicle uponinitial connection of the image capturing apparatus for a vehicle andtransmit the generated data to the server for providing a connectedservice through the communication unit, and the communication unitreceives registration request response data including at least one of atraffic information day use time limit, a parking location imageremaining count, a live image remaining count, and an impact imageremaining count from the server for providing a connected service as aresponse to the terminal registration request.
 16. The image capturingapparatus for a vehicle claim 15, wherein the terminal registrationrequest is repeatedly performed whenever the power of the imagecapturing apparatus for a vehicle is turned on.
 17. The image capturingapparatus for a vehicle claim 10, wherein the control unit adjusts asize of data to be transmitted to the server in consideration of datacommunication speed of the image capturing apparatus for a vehicle withthe server for providing a connected service, a state of a battery ofthe image capturing apparatus for a vehicle, and a size of a storagespace allocated to the server for providing a connected service.
 18. Anon-transitory computer readable recording storage medium containinginstructions that, when executed by one or more processors, cause theone or more processors to perform a method for providing a connectedservice of an image capturing apparatus for a vehicle, the methodcomprising: connecting the image capturing apparatus for a vehicle to aserver for providing a connected service using a wireless communicationmodule; generating event data including event code information andoperation mode information of the image capturing apparatus for avehicle, when an event occurs in the image capturing apparatus for avehicle; and transmitting the generated event data to the server forproviding a connected service through the wireless communication module,wherein the event includes a first event including at least one of animpact occurrence event while parked, an impact occurrence event whiledriving, and a movement occurrence event while parked, the methodfurther includes extracting at least two images of images capturedwithin a predetermined time range of an occurrence of the first eventwhen the first event occurs, and generating image upload data using theextracted images, and in the transmitting of the generated event data,the first event data and the image upload data are transmitted to theserver for providing a connected service through the wirelesscommunication module.